News for hackers. Stuff that matters.
Re:Duck Duck Go Architecture by jwilliams on Friday March 20, 2009 @01:25PM (#525236)
Cool - well I'm on Apache now, on a very undersized server - so I guess I'll have to give nginx a shot.

Not sure how you'd extract more speed from your current setup. The natural next step would be doing work in parallel - this something you do/have considered?

If you do try the Amazon CDN, let us know how you go :)

Re:Duck Duck Go Architecture by epi0Bauqu on Friday March 20, 2009 @02:29PM (#525347)
I use multiple worker processes in nginx (2 x # of cores), which work in parallel. Then FCGI::Engine is configured to run multiple processes as well. Finally, I use the external JS and image files (in part) to speed up the client-side via parallel processing of requests. (Note that IE7 and below limit concurrent connections per host by default often to 2: http://msdn.microsoft.com/en-us/library/cc304129(VS.85).aspx).