How to automatically poke Zope2 on slow requests
I'm trying to debug slow requests/writes, and I'm wondering if there are any suitable tools for this. It's not on every request or write, we're not able to detect manually and start checking from the shell, and we would prefer to not affect performance too much for all the regular requests. What I've been thinking of is a proxy that can start poking with signalstack and perhaps check system IO once a request has taken more than a set number of seconds (or trigger by some other rule), or a component that starts a monitor thread for each request that can do something similar. I'm open to completely different approaches. -- Helge Tesdal www.jarn.com/tesdal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 schrieb Helge Tesdal:
I'm trying to debug slow requests/writes, and I'm wondering if there are any suitable tools for this. It's not on every request or write, we're not able to detect manually and start checking from the shell, and we would prefer to not affect performance too much for all the regular requests.
What I've been thinking of is a proxy that can start poking with signalstack and perhaps check system IO once a request has taken more than a set number of seconds (or trigger by some other rule), or a component that starts a monitor thread for each request that can do something similar. I'm open to completely different approaches.
You're talking of Zope 2.x? Have you checked the publisher events? Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksrcYQACgkQCJIWIbr9KYw2dQCcCbUjvEU3whVzZlzp0W7A7DaO t1QAn2pJdzPSySSQH9fRtMs/7BuFz0m7 =D25U -----END PGP SIGNATURE-----
On 18. des.. 2009, at 13:11, Andreas Jung wrote:
You're talking of Zope 2.x? Have you checked the publisher events?
2.10.6 and RelStorage 1.1.3 in this case. We expect RelStorage 1.4 to help, but still want the debugging thingie. I haven't checked the publisher events, but I guess that's an excellent way of starting and stopping the monitor thread? Or would you use the events some other way? -- Helge Tesdal www.jarn.com/tesdal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 schrieb Helge Tesdal:
On 18. des.. 2009, at 13:11, Andreas Jung wrote:
You're talking of Zope 2.x? Have you checked the publisher events?
2.10.6 and RelStorage 1.1.3 in this case. We expect RelStorage 1.4 to help, but still want the debugging thingie.
I haven't checked the publisher events, but I guess that's an excellent way of starting and stopping the monitor thread? Or would you use the events some other way?
Publisher events are part of Zope 2.12 (not sure if they were backported to older versions). Perhaps of interest: http://pypi.python.org/pypi/haufe.requestmonitoring http://pypi.python.org/pypi/haufe.ztop Andreas - -- ZOPYX Ltd. & Co KG \ zopyx group Charlottenstr. 37/1 \ The full-service network for your D-72070 Tübingen \ Python, Zope and Plone projects www.zopyx.com, info@zopyx.com \ www.zopyxgroup.com - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksrdH4ACgkQCJIWIbr9KYyxuACgiOVBf6yyWyzxfAc5PjqeRgEO nDgAn2HQaagTZUTzfLBZ4G3Hij5Abqmv =qOeE -----END PGP SIGNATURE-----
On 18. des.. 2009, at 13:24, Andreas Jung wrote:
Publisher events are part of Zope 2.12 (not sure if they were backported to older versions).
Perhaps of interest:
http://pypi.python.org/pypi/haufe.requestmonitoring http://pypi.python.org/pypi/haufe.ztop
Thanks, I think this is exactly what we're looking for! :) If the events aren't backported I'm sure we can use the events that are monkeypatched into Zope for cache control. -- Helge Tesdal www.jarn.com/tesdal
Helge Tesdal wrote:
On 18. des.. 2009, at 13:24, Andreas Jung wrote:
Publisher events are part of Zope 2.12 (not sure if they were backported to older versions).
Perhaps of interest:
http://pypi.python.org/pypi/haufe.requestmonitoring http://pypi.python.org/pypi/haufe.ztop
Thanks, I think this is exactly what we're looking for! :)
If the events aren't backported I'm sure we can use the events that are monkeypatched into Zope for cache control.
Talk to Laurence about ZPublisherEventBackport. :) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Helge Tesdal wrote:
I'm trying to debug slow requests/writes, and I'm wondering if there are any suitable tools for this. It's not on every request or write, we're not able to detect manually and start checking from the shell, and we would prefer to not affect performance too much for all the regular requests.
What I've been thinking of is a proxy that can start poking with signalstack and perhaps check system IO once a request has taken more than a set number of seconds (or trigger by some other rule), or a component that starts a monitor thread for each request that can do something similar. I'm open to completely different approaches.
You probably want to enable the trace log, along with maybe another something which logs additional data so that you can correlate with the traced requests. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkssAnIACgkQ+gerLs4ltQ5o+ACgtmu/9v1MwhMw2cUzuKrrVpah dgIAoIKJfVotqfRbeQLkDqaWOM/EXjAc =/LF8 -----END PGP SIGNATURE-----
participants (4)
-
Andreas Jung -
Helge Tesdal -
Martin Aspeli -
Tres Seaver