I've got a site that has 65k products up for sale, and to bring execution time down I started using objectbroker cache more than I've ever done since it came into existence. I've run into some memory issues, and I've narrowed it down to dmHTML objects in the cache.
I've extended dmHTML, with the thought that the maxobjectbroker call would set... well, the max amount of objects stored in objectbroker cache. However, this object has dynamic params that are required to display the type correctly. And that's not an issue, after making sure they're part of the cache call. What I'm seeing though is that one webskin is growing larger over a period of 12-24 hours (#@$@#$#$ bots), and eventually tanks a CPU. The last time I checked, it got up to 2850 webskins cached before I blew away the cache. There were only about 25 actual "objects" in cache, so I'm assuming that's only what counts. Would any of ya'll consider this a bug? I'd rather not avoid caching templates for dmHTML, but need object broker to stop at limit xxxx. __ Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog twitter.com/ophbalance -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
