If you mean 300 really concurrent requests (on average at given moment) then none of reasonable configurations may be sufficient for JIRA (due to its architecture). There are some requests which may take several seconds (at least) - like building more complicated reports, full-text search, some charts, reindex, etc. - in this case your system may starve - as threads (usually around 50 - 200) handling users will be processing their requests longer than yet another users comes in.
However if you have in mind 300 active users who on average use JIRA instance from a few to a few dozens (or even hundreds) times a day - then any currently available decent configuratoin will handle such traffic with so many issues (quad core like any Intel i7 would do).
If the latter holds true, then just invest in:
- multiple core machine (4 physical cores or more would be cool, 8 would be fanstastic). The more really concurrent requests will be handled, the more cores would help - JIRA can do most of the staff in parallel - without blocking other requests.
- fast HDD (SSD for JIRA home would be awesome - indexing takes time)
- at least 8GB of RAM (or rather more if you are going to host DB on the same machine).
My general recommendation: it's really easy to move JIRA from one machine to another, thus I would not overinvest, but rather install JIRA on something "normal" (nothing like 8 x CPUx4, 128GB machines, but some commodity hardware instead) and only if you experience slowness, tweak its configuration (Java memory settings, Tomcat settings, DB connection settings, IO) and only if it does not help, go for a more high-end hardware.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.