We've got digged!

The symfony website made the front page of digg and ajaxian.com this Monday, not to mention the numerous blogs that linked to either the first project tutorial or the new AJAX auto pager feature.

Of course, the influx of traffic was huge, and we've reached records. But we saw no traffic overload. Our server answered every request as fast as usual. Of course the CPU and memory load were a little higher than the day before, but no slowdown could be detected when browsing the site.

Lately, some symfony users worried about symfony performance. Let them be reassured, though: If the symfony website (built with symfony, of course) can bear a digg effect, your website built with symfony will also bear it.

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.


Would you be so kind to share some traffic statistics showing the peak ?
With caching activated, of course.
How many concurrent users did the site receive?
and what of the server you are using? memory/cpu count/cputype/disk RAID10?

zend caching? or eaccellorator

would be good to know what it takes to ride a digg wave.
can you tell us, or maybe publish a page showing statistics of symfony website?
hmm... why is there no response from Francios to all the requests for coming clean with actual stats? what really was "huge" traffic after the digg effect? if they are confident symfony can handle heavy load, why not be real specific? enquiring users who are keen on using symfony want to know!

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.