Timur Kristóf
Timur Kristóf
@degifted Taking a look at [`mdb_cursor_put`](http://www.lmdb.tech/doc/group__mdb.html#ga1f83ccb40011837ff37cc32be01ad91e) it should be quite easy to wrap it. I'll take a look and have a go at it next week.
I would've thought that closing an env would also release the memory map, is that not the case?
Is it possible to reproduce this in C? If yes, then this should be reported against upstream LMDB.
Well, if you have a minimal example in JavaScript that reproduces the issue, then it should be super straightforward to translate that into C.
@kylebernhardy Let us know if you need any help with the C. I think upstream would be interested in hearing about this, if it's not a Node specific issue.
Thank you for taking the time for this writeup. I don't personally use either Windows, or WSL these days, so I can't offer advice, other than a suggestion to report...
If you do come up with a reliable way to test this, or query it from the system, then I'd be happy to include that in node-lmdb. I still believe...
Please show us your benchmark code for both cases that you are measuring.
What happens if the keys are integers? Does that improve performance further, compared to strings?
What exactly would be the benefit of this change? Why does it matter how the keys are sorted?