My contractor gave me some time to test and integrate RocksDB with go etc.
Just for those interested in and playing with optimization:
I added some functions for the iterator which assume to reduce cgo calls, for example: NextValidKeyValue(), which calls a c function that calls the iterator`s next and if valid returns the key and value:
My contractor gave me some time to test and integrate RocksDB with go etc. Just for those interested in and playing with optimization: I added some functions for the iterator which assume to reduce cgo calls, for example: NextValidKeyValue(), which calls a c function that calls the iterator`s next and if valid returns the key and value:
Results:
Not that of an advantage.
Iterator and tests can be found in my fork: https://github.com/kapitan-k/gorocksdb/tree/iterator_perf