<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Benchmarking Performance  (Thread)</title><description> Hello - we are considering using SpiraTeam and we are very interested in how many projects / concurrent users the product can support with an on-premises installation. Are there any guidelines / benchmarks for supported projects/ users?   Ive searched the forums and the installation documentation and dont find something immediately.   best regards - Helen  </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spirateam/best-practices/2356.aspx</link><item><guid isPermaLink="false">threadId=2356</guid><author>Helen Bally (h.bally@itecor.com)</author><title>Benchmarking Performance </title><description> Hello - we are considering using SpiraTeam and we are very interested in how many projects / concurrent users the product can support with an on-premises installation. Are there any guidelines / benchmarks for supported projects/ users?   Ive searched the forums and the installation documentation and dont find something immediately.   best regards - Helen  </description><pubDate>Fri, 12 Feb 2021 18:13:24 -0500</pubDate><a10:updated>2026-04-21T05:17:13-04:00</a10:updated><link>/Support/Forum/spirateam/best-practices/2356.aspx</link></item><item><guid isPermaLink="false">messageId=3922</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> Hi Helen  It depends a lot on the hardware, if you would like to email sales@inflectra.com we can p</title><description> Hi Helen  It depends a lot on the hardware, if you would like to email sales@inflectra.com we can provide some guidelines of the hardware to support a specific # users or the reverse (I have this hardware, how many concurrent users will it support).  Regards  David </description><pubDate>Fri, 12 Feb 2021 18:26:50 -0500</pubDate><a10:updated>2021-02-12T18:26:50-05:00</a10:updated><link>/Support/Forum/spirateam/best-practices/2356.aspx#reply3922</link></item><item><guid isPermaLink="false">messageId=7609</guid><author>Justin Paul (anwermughal42@gmail.com)</author><title> Hi Helen,  SpiraTeam is designed to scale quite well for on-prem installations, and its commonly us</title><description> Hi Helen,  SpiraTeam is designed to scale quite well for on-prem installations, and its commonly used in enterprise environments where both multiple projects and concurrent users are managed together under a single ALM system. It supports  unlimited projects and users , with performance depending more on your server sizing, SQL configuration, and usage patterns rather than a hard cap in the tool itself.  In practice, organizations run from small teams up to hundreds of concurrent users and dozens (or even more) of projects on the same instance, as long as the infrastructure is properly provisioned and optimized. There are no strict public project limits, but Inflectra typically recommends scaling SQL Server resources, indexing, and hardware based on load and concurrency.  If youre planning a rollout, its usually best to size it based on expected concurrent users, test execution load, and integrations rather than number of projects alone.  Also, when preparing reports or architecture diagrams for planning, tools like  pembersih video  are sometimes used to clean up demo recordings so system performance visuals are clearer for stakeholders </description><pubDate>Tue, 21 Apr 2026 05:17:13 -0400</pubDate><a10:updated>2026-04-21T05:17:13-04:00</a10:updated><link>/Support/Forum/spirateam/best-practices/2356.aspx#reply7609</link></item></channel></rss>