I have removed my code with BitSets, this code is more readable, but it
changes public API too mutch.
> > BitSet creates "small" arrays It is important for some JVM
> > implemetations (not trivial to handle memory fragmentation),
> > but possible optimizes nothing on current implementations.
>
>
> BitSet creates "small" arrays It is important for some JVM
> implemetations (not trivial to handle memory fragmentation),
> but possible optimizes nothing on current implementations.
These arrays don't get very big anyway, I expect (you dont have
objects with 100 properties. I can't imagine it b
I have converted code to use BitSet , but see no better performance (not
trivial to test).
BitSet creates "small" arrays It is important for some JVM implemetations
(not trivial to handle memory fragmentation),
but possible optimizes nothing on current implementations.
possible there is no optimiz
I was just having a look over the source of BitSet. It doesn't seem to me
that it would be more performant than a simple boolean[]. (It would
probably consume less _memory_, but that doesn't seem to be a very
critical issue here.) Juozas, why do you expect there to be a performance
gain from using
[EMAIL PROTECTED] Subject: [Hibernate] Dirty checking
and int/boolean arrays
Hi,
I see TypFactory, ClassPersister and all implementations use arrays of ints
to store flags, It is not very performant
and adds some grabage to code. java.util.BitSet is implemented for this use
case (it is possible to implement something faster for this use case too).
Can I break interfaces,
