Hi Marco
Marco Casavecchia Morganti wrote:
I found that after switching the scheduler and the workflow databases of
the CMS into PostgreSQL there is a side effect.
Normally postgresql uses low cpu (expecially if no operations were done)
but when i start the CMS (not the repository) my cpu load makes a step
and remains forever at about 20-23%.
The output of "prstat" (is the "top" version of solaris) tells me that
postgresql is the responsable of the cpu load.
But when i shut down the CMS the cpu load returns at its normal value.
Is this a normal a behavior?
Can I try to make some tuning to prevent this?
It sound like it is not normal behavior ;-)
I'm afraid most people use either MySQL, Oracle or MS SQL Server. I know
of no case in which Hippo CMS with Postgresql is used in production. So
I cannot help you.
Anyone else have experience with Postgresql?
Regards
Niels
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
