История изменений

The performed capacity test has shown that the platform API preserves the desired quality of service only with a limited load. When the number of users simultaneously working with the site goes beyond 70 concurrent user sessions, average response time starts to grow proportionally. When the number of users is about 150, the average response time increases to 5 seconds. See the graph above.

The web server resource utilization especially high CPU utilization level, measured during the testing shows that the performance problems can related to application code and first suspect is Json serialization, because average response Json body size is about 50Kbytes.

The performed capacity test has shown that the platform API preserves the desired quality of service only with a limited load. When the number of users simultaneously working with the site goes beyond 70 concurrent user sessions, average response time starts to grow proportionally. When the number of users is about 150, the average response time increases to 5 seconds. See the graph above.

The web server resource utilization especially high CPU utilization level, measured during the testing shows that the performance problems can related to application code and first suspect is Json serialization, because average response Json body size is about 50Kbytes.

Conclusion

The performed capacity test has shown that the platform API preserves the desired quality of service only with a limited load. When the number of users simultaneously working with the site goes beyond 70 concurrent user sessions, average response time starts to grow proportionally. When the number of users is about 150, the average response time increases to 5 seconds. See the graph above.

The web server resource utilization especially high CPU utilization level, measured during the testing shows that the performance problems can related to application code and first suspect is Json serialization, because average response Json body size is about 50Kbytes.