1
Korak
XOOPS for high traffic site?
  • 2007/2/16 4:54

  • Korak

  • Just popping in

  • Posts: 2

  • Since: 2007/2/16


I have looked at the sites listed as running XOOPS and so far they all seem to be relatively low-volume sites. Is anyone using XOOPS for a relatively high-traffic site? (500,000+ hits per day) We're considering using XOOPS but are pretty worried about how much it might bog down or the hardware requirements to keep it from doing so...

Thanks for any insight you can share...

Korak

2
teibaz
Re: XOOPS for high traffic site?
  • 2007/2/16 7:44

  • teibaz

  • Not too shy to talk

  • Posts: 103

  • Since: 2004/6/13


if average is 63126, then it goes fine :) (Just looked stats)

3
christian
Re: XOOPS for high traffic site?
  • 2007/2/16 8:06

  • christian

  • Just can't stay away

  • Posts: 401

  • Since: 2002/2/24


Hi

Xoops France - January 2007
average hits by days : 260.257
Total for january : 8.067.975

4
JMorris
Re: XOOPS for high traffic site?
  • 2007/2/16 12:07

  • JMorris

  • XOOPS is my life!

  • Posts: 2722

  • Since: 2004/4/11


MyWebResource
Unique visitors per month: 87,630 (January '07)
Page views per month: 264,205 (January '07)

The site's best month saw over 100,000 unique visitors and over 500,000 page views.

That site gets about 1/3rd the traffic of xoops.org and for now, is on a shared hosting package. I'm getting ready to move it over to a VPS so I can add community enhancing features like a forum.

So, to answer your question, if you configure your XOOPS site correctly, it can handle a very large amount of traffic.

HTH.

James
Insanity can be defined as "doing the same thing over and over and expecting different results."

Stupidity is not a crime. Therefore, you are free to go.

5
Korak
Re: XOOPS for high traffic site?
  • 2007/2/17 16:14

  • Korak

  • Just popping in

  • Posts: 2

  • Since: 2007/2/16


Thanks for the feedback! If you have time, do you mind if I ask what the server specs are for your sites? One of the potential knocks on PHP as I understand it is that as a CGI script it doesn't support multi-threading so each instance requires the engine to run an additional time. Am I way off with that? Or does it turn out not to be an issue?

6
birdseed
Re: XOOPS for high traffic site?
  • 2007/2/17 17:28

  • birdseed

  • Just popping in

  • Posts: 59

  • Since: 2005/2/26


Hi

Nice Topic. I am the webmaster of homerecording.de. At the moment, we have about 2 Mio. Page hits per month. There are always about 70-100 people online. We have real performance problems with xoops...but....

The reason is not XOOPS itself. Although my opinion is that the XOOPS core uses too much abstraction rather than trying to safe every unnecessary php command (like the XoopsCriteria and the XoopsObject, for example), it scales very well. There is a constant time of 2-3 seconds needed to run mainfile.php (which is in fact the core). And if php had something like a global object cache, you could even do more performance enhancements. Smarty as the template system is another problem, for example, there is a very bad concept of plugin functions. You can load plugins at runtime, but this is a huge overhead. There should be much more compile-time functiond. But it the end, the core is okay, it uses caching whenever possible, and most queries are finished in microseconds. moreover, it provides a good infrastructure like the MySQL query window, the block caching and the sanitizing of possible register_global injection variables.

The real problems come from the XOOPS modules. CBB, for example, is our "Sorgenkind": We have 650.000 posts in our database. There are many joins which are poorly optimized, we had to manually add missing indices (for example, there was no search index on post_time). The problem is that no one really took the time to optimize those queries. Optimizing a query is a science itself. You would have to look which indices are used and then try to rebuild a query to use better or just other indices. The typical XOOPS sites are rather small communities. They demand many features, performance is not the critical point. Try to ask: Is module X scaling with 100.000 hits per day? - you wont get many answers. I don't complain here, no one gets paid for anything.

Another this is that CBB doesn't implement fulltext search, we had to implement it ourself. Otherwise, you would have to wait for a long time (25 to 30 seconds per request) because CBB uses LIKE '%...%' which is a bad idea for 650.000 posts!!!

There are other modules like the "dictionary" glossary module where there is a word replacement function which is so poor that it will definitely kill your server. AMS - another example - doesn't work without register_globals, we had to fix that.

At the moment, we have a 3.4 Ghz root server with 2 GB RAM. When our contract has ended in October, we will migrate to a bigger server, a dual core with 4 GB as the MySQL backend and a small one as the php frontend. Hope this will solve our problems.

In my opinion, php itself is not the best language for huge websites. There is no type safety, no compiler, no global object cache. Java or .NET are IMHO better candidates. MySQL is a good database server, like Oracle, Sql Server and even Microsoft Acess, but like every other db server, it is not fast "out-of-the-box", every query has to be tested and optimized in order to be fast.

If you expect 500.000 hits per Day, you should really start coding your own customized website system. ASP.NET and C# is a very good combination, other people swear on Java and jsp. Both systems already have their own well-integrated template system, type safety, caching, an application server layer and so on.

greetings
Michael

7
birdseed
Re: XOOPS for high traffic site?
  • 2007/2/17 17:37

  • birdseed

  • Just popping in

  • Posts: 59

  • Since: 2005/2/26


Quote:

Xoops France - January 2007
average hits by days : 260.257
Total for january : 8.067.975


Hi

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?

greetings
MK

8
christian
Re: XOOPS for high traffic site?
  • 2007/2/17 21:46

  • christian

  • Just can't stay away

  • Posts: 401

  • Since: 2002/2/24


Statistiques webalizer
Resized Image

9
ewonline
Re: XOOPS for high traffic site?
  • 2007/2/18 2:30

  • ewonline

  • Not too shy to talk

  • Posts: 198

  • Since: 2004/11/17


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.
Resized Image

10
hervet
Re: XOOPS for high traffic site?
  • 2007/2/18 9:44

  • hervet

  • Friend of XOOPS

  • Posts: 2267

  • Since: 2003/11/4


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 ?

Login

Who's Online

210 user(s) are online (160 user(s) are browsing Support Forums)


Members: 0


Guests: 210


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits