Difference between revisions of "Platform metrics"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 16: | Line 16: | ||
Results are equivilant to 500+ concurrent users | Results are equivilant to 500+ concurrent users | ||
== High volume | == High volume tolerance == | ||
Setup | Setup | ||
| Line 25: | Line 25: | ||
* <2 second reponse | * <2 second reponse | ||
* 320 mB heap size increase | * 320 mB heap size increase | ||
* <1% garbage collection | * <1% garbage collection | ||
== Codebase metrics == | == Codebase metrics == | ||
Revision as of 13:23, 19 February 2013
Performance indicators
Tested on a standard small server year 2012
Setup
- Topology: Seperate frontend / database server
- Hardware: 4 Core CPU, 2 Gb RAM
- Software: Windows, MySQL, Tomcat
- Usecases: login, list, item, update, export
Results
- Frontend server: Average 80% CPU
- Database server: N/A
- Page throughput: 63 requests/second
- Size throughput: 421 kB/second
Results are equivilant to 500+ concurrent users
High volume tolerance
Setup
- 100.000 records, 5 columns each
- 20 mB CSV file size
Results
- <2 second reponse
- 320 mB heap size increase
- <1% garbage collection
Codebase metrics
Project metrics for source version 2090
- Java codebase: 511.242 lines
- Other sources: 159.534 lines
- Designer pages: 488
- Engine classes: 762
- Dependent libs: 90