> I was sitting here thinking; While I will never be slashdotted (Or
> similar violent surge scenarios), there is a good chance that while
> Radiant gains traction, that someone somewhere will end up
> being on the
> blunt end of a slashdotting. Now, I've been brainstorming on
The wikipedia page says that the slashdot affect is somewhere from 'several
hundred through to several thousands' requests a minute.
Radiant caching is much simplier and faster than rails caching, and my
benchmarking of a cached radiant page suggests to me that
radiant on my server should be able to deal with somewhere around 5000
hits/minutes.
I probably wouldn't trust it past 500 hits/second, but I'm pretty sure that my
adsl connection would probably be hosed before
radiant would be, so serving it up with raw apache wouldn't help me. Do you
have enough bandwidth that the app will be your
bottleneck (or conversely, running it on slow enough a server)? Do you really
expect a 5000 hits/minute traffic surge?
(running ab against pages of various sizes):
With splitting of content from data:
296 bytes 114.18 [#/sec] (mean)
1198 bytes 113.63 [#/sec] (mean)
10200 bytes 106.94 [#/sec] (mean)
100202 bytes 82.09 [#/sec] (mean)
1000204 bytes 23.87 [#/sec] (mean)
Using mod_xsendfile:
296 bytes 111.72 [#/sec] (mean)
1198 bytes 111.66 [#/sec] (mean)
10200 bytes 113.44 [#/sec] (mean)
100202 bytes 102.71 [#/sec] (mean)
1000204 bytes 52.12 [#/sec] (mean)
And for comparison, serving html directly with apache:
296 bytes 822.34 [#/sec] (mean)
1198 bytes 811.40 [#/sec] (mean)
10200 bytes 787.08 [#/sec] (mean)
100202 bytes 592.11 [#/sec] (mean)
1000204 bytes 196.89 [#/sec] (mean)
Dan.
_______________________________________________
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
