Software Environment
| Hardware | Adaptation | |
|---|---|---|
Operating system | The designer can be installed in Windows and macOS. The FineReport project can be deployed in Windows, Linux, and Unix.  Note: | |
Database | The following mainstream relational databases and multidimensional databases are supported: Oracle, SQL Server, MySQL, Microsoft Access, Sybase, Db2, PostgreSQL, Apache Derby, and Apache Hive. | |
Server | The Tomcat of 8.5 to 9.0 versions, WebLogic of 12c and later versions, WebSphere of 8.5 and later versions, JBoss of 6.0.0 and later versions, and Resin of 4.0.58 and later versions are supported. | |
Browser | Basic function | Basic functions are supported in Chrome, Firefox, and IE9 and later versions. Chrome is recommended. |
Full screen | The full-screen function is supported by Chrome and Firefox browsers. The full-screen function is supported by IE10 and earlier versions. | |
Extended charts are supported only by Chrome. | ||
Chrome of 86 and later versions is required. | ||
Hardware Configuration
Note:Hardware Configuration Test Instruction
(1) This test conclusion comes from the result of this standard template test. The data is for reference only. Templates in the actual environment may be more complicated. You need to adjust hardware configuration accordingly based on your own environments.
(2) The performance may be affected by the network condition and the database ability to process SQL statements. This test focuses only on the processing duration of FineReport, intranet condition, and non-complicated SQL statement processing (with the network speed and database factors ignored).
Test Conclusion
(1) In standalone scenarios, as the JVM memory increases (from 8 GB to 16 GB and then to 24 GB) when the physical memory is 64 GB, the template response time decreases when the number of concurrent accesses is the same.
(2) As the number of nodes in a cluster increases, the number of concurrent accesses that the system can handle also increases.
(3) If the number of concurrent accesses in a dual-node cluster is twice that in a standalone scenario, and the number of concurrent accesses in a three-node cluster is three times that in a standalone scenario, the average template response time is about the same.
(4) In standalone and dual-node cluster scenarios, the performance of file server sharing is similar to that of automatic synchronization between nodes.
(5) In extreme scenarios where the network is weak and the cluster load balancing fails temporarily, FineReport 11.0 projects are minimally affected.
(6) The performance of preview requiring platform authentication is worse than that of preview not requiring platform authentication. This is because different users cannot share the same result cache.
Recommended Configuration
| Number of Registered Users | Number of Online Users | Number of Concurrent Users | Recommended Configuration | Minimum Configuration |
|---|---|---|---|---|
2000 – 5000 | 400 – 1000 | 0 – 200 | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 16 GB Physical memory: 32 GB | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 8 GB Physical memory: 16 GB |
4000 – 10000 | 800 – 1500 | 200 – 300 | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 16 GB Physical memory: 32 GB | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 8 GB Physical memory: 16 GB |
6000 – 12000 | 1200 – 2500 | 300 – 500 | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 24 GB Physical memory: 48 GB | Standalone CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 16 GB Physical memory: 32 GB |
8000 – 20000 | 1600 – 4000 | 500 – 800 | Dual-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 24 GB Physical memory: 48 GB | Dual-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 16 GB Physical memory: 32 GB |
10000 – 25000 | 2000 – 5000 | 800 – 1000 | Three-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 32 GB Physical memory: 64 GB | Dual-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 24 GB Physical memory: 48 GB |
12000 – 30000 | 2400 – 6000 | 1000 – 1200 | Three-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 32 GB Physical memory: 64 GB | Three-node cluster CPU: 8 cores; 16 threads; 2.4 GHz JVM memory: 24 GB Physical memory: 48 GB |
Definition:
(1) Number of registered users: number of users registered in the system.
(2) Number of online users: number of users who are concurrently online in a certain period of time (generally between 5% and 20% of the number of registered users).
(3) Number of concurrent users: number of users who concurrently send requests to the server (generally between 10% and 25% of the number of online users).
(4) Recommended configuration: The average response time in 70% of scenarios is less than three seconds.
(5) Minimum configuration: The average response time in 70% of scenarios is less than five seconds.
