[osmosis-dev] bug in read simple task, integer overflow

[Brett Henderson]

2013/7/20 Martin Schafran <martin at ampelmeter.com>

> **
>
> I accidently found a 64 bit BitSet.
>
>
> http://lucene.apache.org/core/3_0_3/api/core/org/apache/lucene/util/OpenBitSet.html
>

A bitset is very inefficient if you have sparsely allocated ids.  For this
reason the DynamicIdTracker breaks the id space into small segments and
switches between bitsets and sorted ids for each segment depending on the
id density.

It used to be necessary to manually specify the id tracker depending on
your usage patterns, whereas now DynamicIdTracker provides the best of both
worlds.

I'm happy to be proven wrong, but I'd want to see memory usage numbers
before trying to use another implementation.

Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20130721/154c0331/attachment.html>