Re: ZODB eating CPU but RAM is free

Try increasing the zodb-cache-size for the zope2instance (client1). It defaults to 30000, try increasing it to 100000 and monitor the RAM usage.
Increasing this option means the client side (Zope instance) caches a lot more database objects in its own RAM. This avoids database roundtrips and the latency this incurs. Especially the catalog benefits from having all its many tiny objects inside the client side cache.
Hope this helps,
Hanno

On Wed, Jul 19, 2017, at 08:14, Khurram Shahzad wrote:
> Hi All,
> 
> I am encountering very serious performance issues and I observed that mostly 100% CPU is used and RAM utilization remains less than 15%. Is there anyway that I can configure to increase the RAM?> 
> The problem mostly arises when we query portal_catalog which has about 30,000 objects.> 
> Following is my Plone environment:
> 
>     Plone 4.3.10rc1 (4313)
>     CMF 2.2.9
>     Zope 2.13.24
>     Python 2.7.10 
>     PIL 3.2.0 (Pillow)
> 
> And this is the buildout
> 
> [zeoserver]
> <= zeoserver_base
> recipe = plone.recipe.zeoserver
> zeo-address = 127.0.0.1:8100
> zserver-threads = 8
> zodb-cache-size = 200000
> 
> [client1]
> <= client_base
> recipe = plone.recipe.zope2instance
> zeo-address = ${zeoserver:zeo-address}
> http-address = 8080
> zeo-client-cache-size = 128MB

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.