3 ms·
... and if you only ever make one request, from one user, over and over and over again. ab -n 10000 -c 1 -C '_redmine_session=9ec759408f1ae3c6f919e50baba5a
by kscaldef 17y ago
... and if you only ever make one request, from one user, over and over and over again.
ab -n 10000 -c 1 -C '_redmine_session=9ec759408f1ae3c6f919e50baba5a3dc; path=/' http://127.0.0.1/
Requests per second: 2839.37 [#/sec] (mean)
Time per request: 0.352 [ms] (mean)
Time per request: 0.352 [ms] (mean, across all concurrent requests)
This is an extremely unrealistic workload. It's the best possible scenario for your caches. Yes, he says he was also browsing and editing the site at the same time, but that's still nothing like modeling the real effects of cache invalidation & overflow from many concurrently users.
- sha90 17y agoLooks very much like, at 3k req/s, that request was cached somewhere (either disk/memory/proxy), which are exactly the kind of optimizations the user mentioned you need to think about. Given that you do need to tell Rails when to cache, it may be trivial, but you're still thinking about it.
- newobj 17y agoSeriously... any real load test, IMHO, needs to stem from a capture and replay of live production traffic. Especially if it involves a cache somewhere.