Interrupted IO and AWT

Tue Mar 21 07:18:00 GMT 2000

Bryce> The queue lock is always under contention by the thread(s)
Bryce> putting events onto it and the E.D.T. pulling events off it,
Bryce> and as we know, locking between native threads is slow. I
Bryce> suspect this is the major reason why the user-threads based
Bryce> Sun/Borland JDK 1.2.2 performs so well running JBuilder and
Bryce> other swing apps compared to the other, native threaded JDKs
Bryce> like IBM 1.1.8 (which by all benchmarks has a much superior JIT
Bryce> and memory management) - its thread synchronization is 5x or
Bryce> more faster than linux native locks.
Sometimes I wonder if we should have two locking implementations, one
as fast as possible and one that is perhaps slower but SMP friendly.
Tom