[ZCM] [ZC] 1633/ 1 Request "Lurking CPU eater in Transience"
Collector: Zope Bugs, Features,
and Patches ...
zope-coders-admin at zope.org
Mon Dec 20 12:02:17 EST 2004
Issue #1633 Update (Request) "Lurking CPU eater in Transience"
Status Accepted, Zope/bug+solution medium
To followup, visit:
http://collector.zope.org/Zope/1633
==============================================================
= Request - Entry #1 by evan on Dec 20, 2004 12:02 pm
Status: Pending => Accepted
Supporters added: chrism
Uploaded: "p"
- http://collector.zope.org/Zope/1633/p/view
I foolishly set the timeout of a Transient Object Container to a very high value while leaving the timeout resolution at 20. Subsequent profiling revealed that Transience.py's getTimeslices was using 100% CPU for more than a second every time it was called, which was frequently. This was due to it inserting tens of thousands of elements into the head of an empty list, one at a time. While I learned my lesson, and bumped the resolution up to match the timeout, I also decided to fix getTimeslices. A patch is attached.
==============================================================
More information about the Zope-Collector-Monitor
mailing list