XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Q and A 
  4.  / XOOPS scalability for large site?
Register
11
tommelcher
Re: XOOPS scalability for large site?

  • 2005/9/1 21:10

  • tommelcher

  • Just popping in

  • Posts: 7

  • Since: 2005/9/1 3


Thanks Skalpa!

The detail and intelligence of your reply really enhances the credibility of XOOPS, since you are listed as a "core developer."

We look forward to your roadmap. If we decide to move forward with XOOPS, we hope we can help you with the re-factoring and other enhancements, since they would benefit all XOOPS users (not just us), since everyone wants a zippy site!
12
Herko
Re: XOOPS scalability for large site?

  • 2005/9/1 21:29

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Skalpa leads our core development efforts, a fact that sould help his credibility here And it's good to see you working in the spirit of XOOPS! I hope we can live up to your requirements!

Herko
13
tzvook
Re: XOOPS scalability for large site?

  • 2005/9/1 21:53

  • tzvook

  • Just can't stay away

  • Posts: 875

  • Since: 2003/2/1 2


Hello there:
http://www.trance.co.il had 2,479,902 page views @ Aug 2005 (Range Total: 2,479,902 , Daily Average: 79,996.84) ... Acording to Urchin 5 stats.
Site is on FreeBSD 4.7 + Apache 1.3.33 , PHP 4.3.4 , MySQL 3.23.58 ..... **SHARED SERVER** ( XOOPS 2.1.3 )

Resized Image

Resized Image

Resized Image

Quote:
By "large scale" I mean a site that has more than 1 million users and more than 5 million page views a month. We estimate peak concurrent users at about 100,000.


site is not so interactive lately (we didn't have the time to maintain it the last year, so the amount of transactions is quite low, users are mostely reading, not posting).
I don't think our peaks were more then a few hundreds.
by your numbers it's more likely should be a few milions of page views a day, not a month...

anyway....
since our audiance comes from the whole globe, the load spread on almost 24 hours, which helps a lot.

a few more things:
- we upgraded to MySql 4.1.1 lately and we feel the load now: a lot of database timeouts and so...
- we expirience problems with php.ini (script execution times and so ... ) which begins after about 2000 and require a lot of memory on server and configuring php.ini acordingly.

hope that helps a bit
14
tommelcher
Re: XOOPS scalability for large site?

  • 2005/9/1 22:04

  • tommelcher

  • Just popping in

  • Posts: 7

  • Since: 2005/9/1 3


Thanks for sharing the hard data, tzvook. Do you also have page-served response time data for your peaks?
15
tzvook
Re: XOOPS scalability for large site?

  • 2005/9/1 22:24

  • tzvook

  • Just can't stay away

  • Posts: 875

  • Since: 2003/2/1 2


Quote:

tommelcher wrote:
Thanks for sharing the hard data, tzvook. Do you also have page-served response time data for your peaks?


Sorry, no, I don't have response time in there (I thought I saw it @ Urchin, but nothing in there)

anyway, session graph was forgotten ...

Resized Image

by the way, I wonder if somebody uses MySql from the 4.1x series and has load problems too.
16
pegasus00321
Re: XOOPS scalability for large site?

XOOPS needs work in terms of speed and load especially when the amount of visitors increase.

I have a site that gets around 1M pageviews a month and I've done a lot of work on the backend to speed it up and minimize server resources.
Something that I saw as a big saving is putting the menus in your theme. If you dont install modules very often, it works just fine.

<{if $xoops_isuser}>
<div class="blockTitle">My Accountdiv>
<div class="blockContent">
<table cellspacing="0">
<tr>
<td id="usermenu">
<a class="menuTop" href="<{$xoops_url}>/user.php">Accounta>
<a href="<{$xoops_url}>/notifications.php">Notificationsa>
<{php}>
GLOBAL $xoopsUser;
$pm_handler =& xoops_gethandler('privmessage');
$uid = $xoopsUser->getVar('uid');
$criteria = new CriteriaCompo(new Criteria('read_msg', 0));
$criteria->add(new Criteria('to_userid', $uid));
$msgcount = $pm_handler->getCount($criteria);
$GLOBALS['xoopsTpl']->assign('msgcount', $msgcount);
<{/php}>
<{if $msgcount > 0}>
<a class="highlight" href="<{$xoops_url}>/viewpmsg.php">Inbox (<span style="color:#ff0000; font-weight: bold;"><{$msgcount}>span>)a>
<{else}>
<a href="<{$xoops_url}>/viewpmsg.php">Inboxa>
<{/if}>
<{if $xoops_isadmin}>
<a href="<{$xoops_url}>/admin.php">Admin CPa>
<{/if}>
td>tr>table>div>
<{else}>
<div class="blockTitle">Logindiv>
<div class="blockContent">
<form style="margin-top: 0px;" action="<{$xoops_url}>/user.php" method="post">
Username<br />
<input type="text" name="uname" size="12" value="<{$unamevalue}>" maxlength="25" /><br />
Password<br />
<input type="password" name="pass" size="12" maxlength="32" /><br />
<input type="checkbox" name="rememberme" value="On" class ="formButton" checked />remember me<br />
<input type="hidden" name="xoops_redirect" value="<{$xoops_requesturi}>" />
<input type="hidden" name="op" value="login" />
<input type="submit" value="Login" /><br />
form>
<br />
<a href="<{$xoops_url}>/user.php#lost">Lost Password?a><br />
<a href="<{$xoops_url}>/register.php">Register now!a>
div>
<{/if}>
<{foreach item=block from=$xoops_lblocks}>
<div class="blockTitle"><{$block.title}>div>
<div class="blockContent"><{$block.content}>div>
<{/foreach}>
<div class="blockTitle">Maindiv>
<div class="blockContent"><table width="100%" cellspacing="0" cellpadding="0">
<tr>
<td id="mainmenu">
<a class="menuTop" href="<{$xoops_url}>">Homea>
<a class="menuTop" href="<{$xoops_url}>">Blaha>
<{if $cmodule == 'blah'}>
<a class="menuSub" href="blah2url">Blah Suba>
<a class="menuSub" href="blah2url">Blah Suba>
<{/if}>
td>
tr>
table>
div>


Then to detect which module it is,
stick this in header.php
$cmodule = isset($GLOBALS['xoopsModule']) ? $GLOBALS['xoopsModule']->getVar('dirname') : "system";
$xoopsTpl->assign('cmodule', $cmodule);

If you have caching enabled for a module, it wont work, but to get around that.
Put $xoopsTpl->assign('cmodule', 'modname'); in the actual files for the module.

I foudn this as good way to speed up XOOPS
Pegasus00321


I would appricate it if you click this link
TuFat.com PHP Scripts and etc
« 1 (2)

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

236 user(s) are online (110 user(s) are browsing Support Forums)

Members: 0

Guests: 236

more...

Donat-O-Meter

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

Latest GitHub Commits