1. Environment

Server: qa1-nl.sakaiproject.org (tech specs)
Sakai version: 2.7.0M2
SiteStats version: 2.1.0-b01
Sites:
- 1) 10 sites with SiteStats
- 2) 10 sites without SiteStats (won't process events)
Users: 500 users per site
The Grinder configuration:
- 1 process, 200 threads, 25 runs
- Thread distribution:
  - 50% threads: login, goto a site, download a file, logout (generate a resource event)
  - 25% threads: login, goto a site, logout (generate a site visit event)
  - 25% threads: login, goto a site, access news tool, logout (generate other tool event)

2. Results

2.1. Charts & Raw data

GrinderAnalyzer charts & tables: with SiteStats ON | with SiteStats OFF
SiteStats metrics: with SiteStats ON | with SiteStats OFF
Raw data: svn

2.1. Summary

Test	Test Pass Rate	Concurrent Active Users	Mean Response Time	Resp. Time Std. Dev.	Mean Time to First Byte	# Events Generated in Sakai/sec	# Events Processed by SST/sec	Avg. Time to Process Event
Test (1) sites (SiteStats enabled)	0.981 ⁽¹⁾	150-200 ⁽²⁾	4901.9 ms _(+2.17%)	3596.49 ms	4764.43 ms	34.534	134.231	7 ms
Test (2) sites (SiteStats disabled)	0.856 ⁽¹⁾	150-200 ⁽²⁾	4797.62 ms	3461.35 ms	4683.58 ms	31.357	n.a.	0 ms

Notes

⁽¹⁾: These tests generated so stress that the server ran out of threads available - server responded with 503: Service Temporarily Unavailable. Also, 2nd test (with SiteStats Off) completed with an higher rate of errors, affecting the results (it's faster to process a 503 page than serving processed page from Sakai).
⁽²⁾: This number doesn't reflect typical production numbers of concurrent users or active users - these are highly active users generating activity in milliseconds interval (in a real production system, this could be equivalent to more than 500 concurrent/active users).

Browser not supported