My personal experience so far has confirmed this. Reducing the scope and the
duration of the locks, and allocating individual locks to individual
resources increases the performance and oddly reduces the danger of
deadlocks. I used to spend days tracking deadlock conditions. Hardly
nowadays after allocating individual locks per critical resource, and
carefully defining the scope of each lock. Having single centralized lock is
hardly a good approach.
With best regards,
Boian Mitov
--------------------------------------------------------------------
Mitov Software
http://www.mitov.com
--------------------------------------------------------------------
----- Original Message -----
From: "Florian Klaempfl" <[EMAIL PROTECTED]>
To: "FPC developers' list" <fpc-devel@lists.freepascal.org>
Sent: Thursday, July 31, 2008 3:23 AM
Subject: Re: Multi threading support was Re: [fpc-devel] Russianlocale
information not compatible withFPClocale variables
Come one, it's not that hard to understand :): synchronized might allow
the same way of working: first, you work with big locks, later to add more
fine granulated ones.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
