For 200 concurrent users or up to 2000 casual users:įor the tests providing these metrics, a Dell Poweredge Server 2600 dual Xeon CPU 32bit machine was used:Ģx Intel Xeon 2.8GHz (533Mhz FSB, single-core)Īlfresco Enterprise 2.1 and MySQL 5 on Windows 2000 with Tomcat was deployed onto the server.For 100 concurrent users or up to 1000 casual users:.For 50 concurrent or up to 500 casual users:.Suggested memory+CPU settings per server: Note that for these metrics, N concurrent users is considered equivalent to 10xN casual users that the server could support. You will need to add CPUs depending on the complexity of the tasks you expect your users to perform and how many concurrent users are accessing the client. However - you will need to add additional memory as your user base grows. This means you can run the Alfresco repository and web-client with many users accessing the system with a basic single CPU server and only 1024MB of memory assigned to the Alfresco JVM.
The Repository L2 Cache plus initial VM overhead plus basic Alfresco system memory is setup with a default installation to require a maximum of approximately 1024MB. JVM Memory and CPU Hardware for multiple users Benchmarking your environment is necessary to get a precise understanding of what resources will be required. Para-virtualization, or virtualized accesses to native host volumes will not require as many resources. When using the rough sizing requirements below, it might be necessary to allocate twice as many resources for a given number of users when those resources are virtual. atomic or background indexing) there may be some additional overhead as the content is indexed or meta-data extracted from the content in each file.Īlfresco runs well when virtualized, but you should expect a reduction in performance. The overhead of writing content is also low but depending on the indexing options (e.g. The overhead of the Alfresco server itself for reading content is very low as content is streamed directly from the disks to the output stream. The performance of reading/writing content is almost solely dependent on the speed of your network and the speed of your disk array. It is highly recommended that a server class machine with SCSI RAID disk array is used. You should also make sure there is sufficient space overhead for temporary files and versions - each version of a file (whether in DM or WCM) is stored on disk as a separate copy of that file, so make sure you allow for that in your disk size calculations (and, for DM, use versioning judiciously). Content in Alfresco is by default stored directly on disk, therefore to hold 1000 documents of 1MB in size will require 1000MB of disk space. The size of your Alfresco repository defines how much disk space you will need and is a very simple calculation.
Our benchmarks show a significant performance gain when using 64 bit hardware and a 64 bit JRE. However, to get optimum performance, we recommend the following: Īlfresco degrades gracefully on low powered hardware, and small installations can run well on any modern server. The metrics and estimates below are only a suggestion and your system may vary. You should tune the memory and garbage collection parameters for the JVM as appropriate for your use-case. The Alfresco Repository and web-client hardware requirements are variable and depend significantly on the number of concurrent users that will be accessing the system.
6.2 Permanent Generation (PermGen) Size.5 JVM Memory and CPU Hardware for multiple users.