|
Sunday 02 September 2007 12:07:30 pm
php.ini won't help you there, it's your mysql configuration that are wrongly configured or you simply have reach the limit of your setup. I'll guess mysql is set up wrong since ez publish tends to wear out php/apache before mysql, if mysql is set up correctly. Mysql comes with quite conservative settings by deafult, so there is a lot you can do. How you set it up depends highly on the server, first and foremost how much RAM it has. Since you really don't want mysql to swap it's memory cache to the hardrive.. Here is the more or less the settings used on a linux box that had the same problem recently since the hoster used default mysql settings:
max_connections = 300
thread_cache_size = 50
query_cache_size = 64M
sort_buffer_size = 3M
key_buffer = 256M
table_cache = 3000
Btw, one of the best written tuning articles for mysql can be found right here on ez.no:
http://ez.no/community/articles/tuning_mysql_for_ez_publish
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
