The background -
We will be sending a newsletter out to 60,000 people and we wanted to see what kind of load Concrete5 could handle.

I setup a VPS with 3GB Ram (burstable to 4GB), 5 Cores... It's pretty quick, disk speed about 120 MB / Sec...

I'm testing using Siege on a VPS in the same datacenter with similar specs.

These results are not scientific at this point.. I'm going to do a little more controlled testing, and put together an excel datasheet in the next week or so.

* My biggest concern was how many users can a standard concrete5 install handle.
* What kind of latency issues will we run into
* What is the best caching method (default)

All of these are tested on 5.4.1.1, with a custom theme, but no add-ons.

I used TOP to view the server load, however I didn't do that on the first round of testing...
Hope this helps.
(Analysis)
Caching really helps, nearly twice as many users can be served... Shortest transaction nearly 1/3 that of cache disabled. Server load observed seemed lower with cache enabled.

50 Concurrent Users in 30 seconds.

Cache Disabled:
#1
ransactions: 150 hits
Availability: 100.00 %
Elapsed time: 29.91 secs
Data transferred: 1.40 MB
Response time: 6.67 secs
Transaction rate: 5.02 trans/sec
Throughput: 0.05 MB/sec
Concurrency: 33.46
Successful transactions: 150
Failed transactions: 0
Longest transaction: 24.18
Shortest transaction: 1.27

#2 (Load ~ 22)
ransactions: 210 hits
Availability: 100.00 %
Elapsed time: 30.04 secs
Data transferred: 1.96 MB
Response time: 5.09 secs
Transaction rate: 6.99 trans/sec
Throughput: 0.07 MB/sec
Concurrency: 35.59
Successful transactions: 210
Failed transactions: 0
Longest transaction: 19.20
Shortest transaction: 0.60

#3 (Load ~18.26)
ransactions: 205 hits
Availability: 100.00 %
Elapsed time: 29.87 secs
Data transferred: 1.91 MB
Response time: 5.20 secs
Transaction rate: 6.86 trans/sec
Throughput: 0.06 MB/sec
Concurrency: 35.68
Successful transactions: 205
Failed transactions: 0
Longest transaction: 24.63
Shortest transaction: 0.66




Cache Enable - Block Level
#1
ransactions: 359 hits
Availability: 100.00 %
Elapsed time: 29.53 secs
Data transferred: 3.35 MB
Response time: 3.09 secs
Transaction rate: 12.16 trans/sec
Throughput: 0.11 MB/sec
Concurrency: 37.58
Successful transactions: 359
Failed transactions: 0
Longest transaction: 19.28
Shortest transaction: 0.33

#2 (Load ~17)
ransactions: 378 hits
Availability: 100.00 %
Elapsed time: 29.82 secs
Data transferred: 3.52 MB
Response time: 2.74 secs
Transaction rate: 12.68 trans/sec
Throughput: 0.12 MB/sec
Concurrency: 34.71
Successful transactions: 378
Failed transactions: 0
Longest transaction: 13.10
Shortest transaction: 0.39

#3 (Load ~7)
ransactions: 288 hits
Availability: 100.00 %
Elapsed time: 29.58 secs
Data transferred: 2.69 MB
Response time: 3.64 secs
Transaction rate: 9.74 trans/sec
Throughput: 0.09 MB/sec
Concurrency: 35.44
Successful transactions: 288
Failed transactions: 0
Longest transaction: 13.70
Shortest transaction: 0.67

#4 (Load ~ 15.5)
ransactions: 311 hits
Availability: 100.00 %
Elapsed time: 29.54 secs
Data transferred: 2.90 MB
Response time: 2.62 secs
Transaction rate: 10.53 trans/sec
Throughput: 0.10 MB/sec
Concurrency: 27.55
Successful transactions: 311
Failed transactions: 0
Longest transaction: 14.54
Shortest transaction: 0.34



Cache Enabled - Emergency Cache
#1
ransactions: 379 hits
Availability: 100.00 %
Elapsed time: 29.66 secs
Data transferred: 3.53 MB
Response time: 2.89 secs
Transaction rate: 12.78 trans/sec
Throughput: 0.12 MB/sec
Concurrency: 36.91
Successful transactions: 379
Failed transactions: 0
Longest transaction: 16.29
Shortest transaction: 0.37

#2 (Load ~15.4)
ransactions: 376 hits
Availability: 100.00 %
Elapsed time: 30.07 secs
Data transferred: 3.51 MB
Response time: 2.96 secs
Transaction rate: 12.50 trans/sec
Throughput: 0.12 MB/sec
Concurrency: 37.04
Successful transactions: 376
Failed transactions: 0
Longest transaction: 24.59
Shortest transaction: 0.36


-Phil