Piotr Balcer
Piotr Balcer
This was done halfway in 1.7, and I still have some work on branches that I want to push out. Hopefully in 1.8 time-frame.
No, this is an internal allocator optimization that's trying to decouple metadata and data of persistent allocations. The fact that you can run pmempool info with an open pool on...
I this we should close this. I agree with Krzysiek. @marcinslusarz @dawidpaluszkiewicz
We haven't yet reached a point where we feel we have enough changes accumulated to warrant a release, but we can prioritize work accordingly and be flexible on a specific...
Makes sense. I just created a PR with the proposed changes - can you take a look to see if the API is sensible and would work for you? ```...
No, this is purely a runtime thing.
@jolivier23 we've merged this change, so, if you want, you can now start integrating this feature in your codebase. Our plans right now are to release 1.11 in late May/early...
My intention was to tag a release this week. Everything is ready, apart from a fix for #5197, which has proven difficult (who doesn't love makefiles...). If everything goes according...
@seghcder Yes, to properly implement this functionality, we'd need a way for group transaction commit. And now when I think about how the API would look like, we would also...
It's interesting that you observe higher performance using multiple pools. What's the size of the allocations? The one reason that I can think of for your observed behavior is that...