Okay, I see the point: It is hits per day, not pages per day which you were talking about. Thank you for showing the webalizer statistic. Hits are simply request which the webserver receives. This can be graphics, download files etc. Pages per day is the relevant criteria here - quasi the amount of php pages. You have around 60.000 pages per day. We have around 80.000 pages per day which is comparable to xoops.fr. If you say that you don't have any performance problems, I assume the reason is that the amount of forum posts is less (about 80.000 instead of 650.000).
[quote] what a "kind" answer... Are you sure of you own statistics ? [/quotes]
Yes. Webalizer. Was my answer unkind in any form?
[quote] Or anyone else - I'm very interested in changes that you made in XOOPS and modules ... [/quotes]
If there was a simple switch "make XOOPS faster", the developers would already have turned it on. There are some standard ways like caching blocks or installing eAccelerator. Another thing is to optimize slow queries. Usually, i expect that well developed modules already had done this.
greetings MK
Re: XOOPS for high traffic site?
by stefan88 on 2007/2/18 10:14:15
@ewonline Quote:
hack the XOOPS code like heck, which I've done
Can you share those hacks ...?
Or anyone else - I'm very interested in changes that you made in XOOPS and modules ...
you can mail me at leed8888-at-gmail.com
Thanks
Re: XOOPS for high traffic site?
by hervet on 2007/2/18 9:44:56
Quote:
birdseed wrote: Are you sure that these are real page requests? This would mean that you get 8 Mio. banner Impressions per month. Please make sure that this number is correct. You have about 1 posting in 20 minutes, we have about 10 times more postings. Where do the requests come from?
what a "kind" answer... Are you sure of you own statistics ?
Re: XOOPS for high traffic site?
by ewonline on 2007/2/18 2:30:43
I run a XOOPS site with 2M page views (6M+ hits), and about 70,000 Unique Visitors per month and I can tell you it used to be a huge problem. The fix, hack the XOOPS code like heck, which I've done. A lot of unused features in XOOPS I have removed. Also, install eAccelerator, that definitely helps a lot.
Installing eAccelerator will help a lot, but not get page gen times down to the 0.0x levels, just down to 0.x levels.
And I agree, its not entirely XOOPS' fault, its a CMS, its dynamic, so its that way by nature.