Forums / General / slow site / cache dir not being populated

slow site / cache dir not being populated

Author Message

Andre Felipe Machado

Sunday 01 July 2007 8:20:36 am

Hello,
My site http://www.techforce.com.br is working but painfully slow and cpu hungry now after an isp bw quota limit reached.
The mysql db was runing away 100% cpu.
Myisamchk --safe-recover on it.
Myisamchk --extend-check on it said mysql ok now.
But the site is still slow and now apache is taking 100% cpu.
I guess it is a cache problem.
the settings/override/site.ini.append.php contains:

[OverrideSettings]
Cache=enabled

[TemplateSettings]
TemplateCache=enabled
TemplateCompile=enabled
TemplateOptimization=enabled
NodeTreeCaching=enabled

[ContentSettings]
TranslationList=eng-GB;eng-US;por-BR
ViewCaching=enabled
CachedViewModes=full;sitemap;pdf
PreViewCache=enabled
PreCacheSiteaccessArray[]=news
PreCacheSiteaccessArray[]=news_admin

Executed bin/shell/clearcache.sh --clear-all
Executed bin/modifx.sh
Granted permissive access to var/
changed var/ owner to the webserver user and group.
Even restarted the xen vm.

but the var/news/cache and var/cache sub-directories are almost empty (only packages and translation populated).
I saw that var/news/cache/expiry.php was not cleared by clearcache.sh.

Do you have suggestions?
Regards.
Andre Felipe

---
A Debian user never dies. Issues a last command:
shutdown -h now

http://www.techforce.com.br

Paul Borgermans

Sunday 01 July 2007 11:22:48 am

If mysql is running away, check also the session table (and clear it).

Hard to do anything about bw limits hit

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Andre Felipe Machado

Monday 02 July 2007 8:28:31 am

Hello,
Many thanks for your suggestion. I was not aware of the session table problem.
I managed to circumvent the cache problem (not a real solution).
Was able to find a local backup (rsync) including the var/cache and var/news/cache directories with megabytes of data and done at a day with normal behaviour.
Uploaded that old cache data and now the site is running at normal speed.
Some pages were displaying at old cached versions (!) from that date, despite admin interface showing their new versions.
Well, an edit publish cycle refreshed the cache content for these pages. Not the best solution, but worked.
From inside the admin panel, flushing the cache did not solve.
Weird. Seems as ezp not being able to create cache directories or files. but it can update content and recreate cache files already there.
It is a trick, and a real solution should be investigated.
regards.
Andre Felipe

---
A Debian user never dies. Issues a last command:
shutdown -h now

http://www.techforce.com.br