When setting a Max-size for Attachments in JIRA, what are people experiencing as boundaries where performance somewhat and then significantly degrades?

Beth Schaeferma

I am considering the approval of a bump-up to 20MB for max size for attachments in JIRA. Instructions for doing so are here, but there is no contextual guidance for an acceptable range before you might experience negative results in performance:

http://confluence.atlassian.com/display/JIRA/Configuring+File+Attachments

The reasons for doing so are that I have teams with large log files that they don't want to push into document repositories due to inconvenience and overhead of doing so. Other scenarios I could imagine would be attaching larger presentations or vids to issues.

If 10MB is the assumed sweet-spot, does anyone have anecdotal feedback on pushing past this and discovering thresholds for when performance degrades marginally (i.e. maybe 50MB - It's a bad idea to move past this) and then significantly (i.e. maybe 100MB - If you do this, you will kill your instance)? Or are there too many factors at play in individual system set-ups to make shared observations relevant?

JamieA

I don't think it makes a blind bit of difference to performance, and I doubt there is a tipping point. All jira is needs to do is stream the file when the client requests... not demanding.

Obviously it will have an effect on the disk space you require, but I presume you've factored that in.

The only possible difference is, there is a plugin that indexes attachments, which would push up the size of your index. I wouldn't recommend using this plugin if you are storing large log files.

> If 10MB is the assumed sweet-spot,

I don't think 10Mb is a sweet spot, it's just an arbitrary round number.

Note s.a.c allows attachments up to 250Mb - if there was a problem they wouldn't do this.