Re: Performance issue on dedicated server

"Panayiotis Dionyssopoulos" <pdion-Pa7mVGAsjv/[email protected]>
Newsgroups gmane.comp.cms.xaraya.user
Message-ID <[email protected]>
Guys thanks for your response.
I do have a lot of both articles and categories.

I will try removing some obsolete category trees, maybe this will help.

We will also be upgrading the memory and try some apache/mysql
optimizations, 512MB seems to be small and anyway ram prices are very low.

-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Todd Holden
Sent: Wednesday, January 09, 2008 9:51 PM
To: Xaraya User List
Subject: Re: [Xaraya_user] Performance issue on dedicated server


This in addition to John's good advice.  We have experienced similar  
behavior.  We determined:

1.  It almost always coincides with search engine indexing,  
particularly MSN.  MSN seems to index by making multiple simultaneous  
requests from their database, rather than spidering a site in the  
traditional sense.  Thus, the database has to contend with a request  
rate that is above the baseline and becomes prone to choking.

2.  The queries that slow things down are usually associated with  
large DD joins.  Sometimes, though, article map and multi-category  
summary views (e.g. c_35&c_22&c_120 etc.) are to blame, especially if  
you have a large set of articles.  If you do not have any use for  
those particular views, you may benefit from some selective templating  
to make them inaccessible.  Disqualifying them using robots.txt proved  
ineffective, as MSN seems prone to disregard ignore entries if the  
pages have already been indexed.

3.  If you haven't already, turn on slow query logging in the MySQL  
config.  This will provide a good picture of which queries are using  
up your resources.

Hope this helps,


T.



On Jan 8, 2008, at 10:18 PM, John Cox wrote:

> On Jan 8, 2008 4:46 PM, Panayiotis Dionyssopoulos  
> <pdion-Pa7mVGAsjv/[email protected]>
> wrote:
>
>>
>>
>>
>>
>> "Normal Xaraya error processing has stopped because of an error
>> encountered.
>>
>> The last registered error message is:
>> PHP Error code: 2
>> At:
>> /var/www/vhosts/eurobath.gr/httpdocs/xaradodb/drivers/adodb- 
>> mysql.inc.php
>> (Line: 355) mysql_connect(): Too many connections
>>
>> "
>>
>> while other times the site is just unresponsive.
>
>
> I believe there is a setting to use either persistent or non- 
> persistent
> connections in the config file.  Ensure that you are not using the
> persistent connections.  Also, check your auto-cache / sessionless  
> cache
> settings.  I believe there is a tutorial on xaraya.com that gives  
> some good
> guidance on the subject.  My guess is with the increased traffic,  
> you are
> also seeing a spike of spider traffic.
>
> The problem with any framework is for flexibility and faster  
> development
> time, you tend to have a higher cost in hardware.  I justify this  
> business
> case with people cost more than hardware any day of the week, but  
> that's
> something that you need to think about just a bit.  For instance:
>
> SELECT foo.bar
>             bar.foo
> FROM foo foo
>
> LEFT OUTER JOIN bar bar
> on foo.bar = bar.bar
>
> is going to be more performance friendly than:
>
> SELECT foo
> FROM foo
>
> SELECT bar
> FROM bar
>
> but with xaraya you are more apt to see more individual queries than  
> the
> joined queries just due to the nature of the beast.  So you are  
> always going
> to give up some performance over what could be written on a one-off  
> basis.
> Cache should take care of some of the problems, but there is always  
> going to
> be the cases where the cache has to be built.
>
> hth a bit,
>
> jc
> _______________________________________________
> Xaraya_user mailing list
> [email protected]
> http://xaraya.com/mailman/listinfo/xaraya_user

_______________________________________________
Xaraya_user mailing list
[email protected]
http://xaraya.com/mailman/listinfo/xaraya_user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.