Need for more profiling...

[lemire]

Though the code is well tested and works, and there has been several contributions to make it run faster, there could still be large inefficiencies. We should profile this code.

http://blog.golang.org/profiling-go-programs

[lumost]

Is it known how close the golang implementation is in performance to other roaring bitmap implementations?

cheers,

--James

[lemire]

@lumost

No. Sadly.

Not that it is hard to find out. Someone needs to do the leg work...

Here is a comparative benchmark in C/C++...

https://github.com/RoaringBitmap/CBitmapCompetition

I strongly encourage work in this direction.

[lemire]

@lumost Here is a Go benchmark that compares three implementations

https://github.com/lemire/gobitmapbenchmark

It looks like github.com/RoaringBitmap/roaring does well.

[brentp]

where is the benchmark?

[lemire]

https://github.com/lemire/gobitmapbenchmark

[lemire]

The benchmark has been extended considerably: see https://github.com/lemire/gobitmapbenchmark

The Go version of Roaring fares well. In fact, I am now preoccupied with the performance of the C version.