RE: Some more locking related changes
"Garth T Kidd" <garth-OnzZ1s1DREKDegMON/[email protected]> Tue, 28 Sep 2004 07:39:05 +1000
| Newsgroups | gmane.comp.pythin.pyds.devel |
|---|---|
| Organization | Deadly Bloody Serious |
| Message-ID | <[email protected]> |
The more locks gone, the better; a lot of people I've suggested PyDS to have bounced it for being too gluggy. Even without my lock debugging code. It does seem a lot nipper now, I must say. In turn, I've got to go through WikiTool and MeshTool removing all my silly "try to avoid acquiring twice" code. I hadn't realised at the time that RLock was perfectly happy doing that. :) -----Original Message----- From: pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected] [mailto:pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected]] On Behalf Of Bauer, Georg Sent: Monday, 27 September 2004 7:34 PM To: PyDS Developer List (E-Mail) Subject: [Pyds-dev] Some more locking related changes Hi! I just worked a bit on the CalendarTool to remove unnecessary locks in _findCache (and removed some more even more unnecessary locks - only write access and internal structure changes should be blocked with locks), so now the CalendarTool should produce much less lockings and so shouldn't be too much of a problem. Before this change the CalendarTool was the main source for active locks in PyDS. bye, Georg _______________________________________________ Pyds-dev mailing list Pyds-dev-iYtK5bfT9M//Ad8WF/[email protected] http://www.westfalen.de/cgi-bin/mailman/listinfo/pyds-dev