Hi there,
Just trying to gauge if CMSMS would be a good match for a busy site - say 100k page views a day. Has anyone had similiar experiences with busy sites?
I understand Smarty is used for the templating so I guess there are content cacheing mechanisms in place?
Appreciate any help.
Thanks,
Guy
Performance for busy sites?
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Performance for busy sites?
Well, I'm using cms 0.11.2 on a simple 1.8Ghz machine, 1G of ram, with about 4 million page views per month (on a good month), and it stands up rather well.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Performance for busy sites?
i was wondering this myself.. how the fully db-driven cmsms compares to other cms packages in terms of server load and page rendering speed.
eternity (n); 1. infinite time, 2. a seemingly long or endless time, 3. the length of time it takes a frozen pizza to cook when you're starving.
4,930,000,000 (n); 1. a very large number, 2. the approximate world population in 1986 when Microsoft Corp issued its IPO. 3. Microsoft's net profit (USD) for the quarter (3 months) ending 31 March 2007.
CMSMS migration and setup services | Hosting with CMSMS installed and ready to go | PM me for Info
4,930,000,000 (n); 1. a very large number, 2. the approximate world population in 1986 when Microsoft Corp issued its IPO. 3. Microsoft's net profit (USD) for the quarter (3 months) ending 31 March 2007.
CMSMS migration and setup services | Hosting with CMSMS installed and ready to go | PM me for Info
Re: Performance for busy sites?
With proper caching and other tricks (that we do a lot of already), it shouldn't be an issue. The db is pretty much only getting timestamps for most data to make sure that it hasn't been updated. It does the template and content check in 1 query. On an average, CMSMS only does 10-20 queries per page.
could there be a scaling issue eventually? Sure. But I think that the amount of traffic that those sites are going to get is beyond the scope of CMSMS anyway. Plus, you can always throw hardware at the problem...
could there be a scaling issue eventually? Sure. But I think that the amount of traffic that those sites are going to get is beyond the scope of CMSMS anyway. Plus, you can always throw hardware at the problem...