Kuros Yalpani wrote: > actually, this would presumably answer my question, since if > hyperthreading is emulating multiple cpu's then the multiprocess > architecture of fcgi would benefit from that. However, I am not sure on > how load "mutual exclusivity" affects cache usage. Do you mean a kind of > instruction cache? Any Idea on how mongrel vs lighttpd behaves?
Sure, multi-process architectures can leverage SMP architectures. But my point is: be aware that having two equal processes run on two HTT CPU's (so actually a single CPU) will be detrimental to performance, generally. The same code will be running on the same physical CPU components and that needs to run serially, with all of the cache and context issues that brings with it. I prefer a cluster of Passengers, Mongrels or Thins (depending on your performance profile) over FastCGI because I find it to be more stable and easier to manage. I also find the Apache / Nginx / Lighttpd discussion to be a bit of a bike-shed when it comes to serving dynamic Rails requests. The performance differences are not significant except for static assets or when you're pressed for RAM. All these deployment options are process-based. Apache can run multi-threaded too. I don't have any production experience with that. -- Roderick van Domburg http://www.nedforce.com -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
