--On 24. April 2008 07:38:14 -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote:
I'd like to know how to avoid such a situation. Would slices have helped here? No. Slicing would make things worse by increasing lock contention.
OK, thanks.
Since all the posts were for one list, and since the list is locked by IncomingRunner for the entire duration of it's processing of a message, slicing wouldn't help. It normally helps by increasing parallelism, but only if the load is across multiple lists so the the sliced runners aren't blocking each other.
With only 2 to 3 messages per minute under normal conditions that doesn't seem to be necessary for us.
In this case, IncomingRunner was doing the best that could be done. I see that VirginRunner was involved in the locking, so perhaps these messages were being held and moderator notices were being generated. Then perhaps a moderator went to the admindb interface, which can keep a list locked for a long time if it is processing a large list of requests.
Ah, I wasn't even aware of that. Anyway, they promised not do it like that anymore, so I guess we're fine. Thanks for your help!
--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
.:.:.:.Skype: shagedorn.:.:.:.
pgpfalcN7yRFb.pgp
Description: PGP signature
------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
