Interrupted IO and AWT

Wed Mar 22 17:10:00 GMT 2000

Ideally, I'd like to see measurements of collections of representative real
applications with various locking strategies :-).
Realistically, any measurements are much better than none. My guess is that
even the following microbenchmark would yield some insight:
1) Acquire and release a single lock in a single thread in a tight loop.
2) Do (1) concurrently with different numbers of threads on different number
of processors, all acquiring the same lock. 
This is hopefully an unrealistically bad case, but it's probably more
representative of real applications than it should be. 
(Running a bunch of allocation tests concurrently essentially behaves like
this, if there is no per-thread allocation buffer. I've certainly seen
interesting variation in the results. I also thought someone posted test
results along these lines for some other locking schemes, but not spin locks
with exponential backoff.)
Hans
-----Original Message-----
From: Jeff Sturm [ mailto:jsturm@sigma6.com ]
Sent: Tuesday, March 21, 2000 12:20 PM
To: Boehm, Hans
Cc: Tom Tromey; Bryce McKinlay; java-discuss@sourceware.cygnus.com
Subject: Re: Interrupted IO and AWT
"Boehm, Hans" wrote:
[Exponential back-off spin locks:]
> For some strange reason, that's a scheme that's rarely discussed in the
> literature. Does anyone have some real measurements that include
something
> like this scheme?

No. What would you suggest measuring? I'm interested in it but
somewhat lacking in experience.