-Original Message-
From: Ivan Zhakov [mailto:i...@visualsvn.com]
Sent: woensdag 27 augustus 2014 15:29
To: Bert Huijben
Subject: Re: [Patch] R/W lock slowness on Windows (Was: Windows R/W lock
comment / Reader Writer lock performance on Windows)
Hi Bert!
Did you get any
On 27 August 2014 17:34, Bert Huijben b...@qqmail.nl wrote:
-Original Message-
From: Ivan Zhakov [mailto:i...@visualsvn.com]
Sent: woensdag 27 augustus 2014 15:29
To: Bert Huijben
Subject: Re: [Patch] R/W lock slowness on Windows (Was: Windows R/W lock
comment / Reader Writer lock
On 2 August 2014 13:02, Bert Huijben b...@qqmail.nl wrote:
Hi,
With this mail I would like to ping the original problem with the second
patch I send to the list. This patch doesn't have the likely original
problems of potentially changing the lock behavior to a spin lock, but
Hi,
With this mail I would like to ping the original problem with the second
patch I send to the list. This patch doesn't have the likely original
problems of potentially changing the lock behavior to a spin lock, but
provides all the performance improvements anyway.
It just replaces the
mutex.
(Handling this mutex is where the current implementation spends almost all its
time)
Bert
From: Jeff Trawick [mailto:traw...@gmail.com]
Sent: donderdag 3 juli 2014 21:57
To: APR Developer List
Subject: Windows R/W lock comment
I'm getting filtered when I try
[mailto:b...@qqmail.nl]
Sent: maandag 7 juli 2014 12:25
To: 'Jeff Trawick'; 'APR Developer List'
Subject: RE: Windows R/W lock comment
I think it is a hybrid loop, but the documentation is not really clear about
it. It is not as hybrid as a critical section (which internally falls back
[mailto:b...@qqmail.nl]
Sent: maandag 7 juli 2014 12:25
To: 'Jeff Trawick'; 'APR Developer List'
Subject: RE: Windows R/W lock comment
I think it is a hybrid loop, but the documentation is not really clear about
it. It is not as hybrid as a critical section (which internally falls back
I'm getting filtered when I try to respond to the original thread.
This is an important issue: If a writer holds the lock for a significant
time (e.g., refreshing a table from a database), do all would-be readers
spin-loop, or is it a hybrid spin-then-sleep solution? We should know this
for
