Are you sure that BitSet should be internally synchronized ?
I cannot find such statement in specs. In classpath version precaution
was taken to avoid deadlocks. Together with two synchronized statements
it introduces a lot of overhead.

I think that jdk BitSet is not synchronized and thus to become treadsafe
one have to implement syncrhonization by hand anyway. And classpath
implemenation will double it, again giving overhead.

Speed difference is really great - something like 3 or 4 times.


Artur

Reply via email to