Can anyone ring in with their experiences with EE’s performance on large-scale or complex sites?
By “large-scale”, I mean a site featuring 20+ channels with dozens or even hundreds of entries each, multiple sites running under MSM, a common membership base across MSM, and forums.
What have your experiences been with EE regarding performance, DB load, server load, page load times, security, crashes / data loss, etc on such large-scale sites?
I’m developing a site for a university faculty, involving almost a dozen subsites for individual departments, which I’m planning to implement with MSM. However, I am a little concerned with putting so many eggs in one proverbial basket.
Is EE going to be able to handle this?? What happens if the site is getting an average of 1,000+ hits/day? Is the DB going to tank?
I developed a query-intensive site in EE previously, and had to install Static Page Caching to offset the DB load, because my server was just getting hammered. Granted, it was probably my query-heavy template design at fault, but still… It’s made me a little gun shy when it comes to EE’s capacity to handle a huge load. Perhaps this is true of any system.
Any tips for optimizing / planning architecture for a large site?
I’m curious about Snippets in EE2.0, for instance—does anyone have any experience with using these to offload DB queries? Most content I’ll be pulling will not need to be 100% dynamic. Some caching is fine. What worries me is membership—if 100+ people are logged into the site, is this going to cripple the server?
Any advice / thoughts / feedback / experiences you can share would be appreciated! Thanks!