Closed SchrodingerZhu closed 1 year ago
No worries. I have a large pile of changes coming, so I haven't worried about this. Yeah, I dropped that option as it was added complexity and didn't have real benefit.
So most of the changes are in now. Do you think you would be able to do a beta release of the crate?
There was a primitive one at https://crates.io/crates/snmalloc-rs/0.3.0-beta.1+f1be609 tracking early stage snmalloc 2. I will do a dependency bump to trace latest upstream!
With the release of 0.6.0 it would be good to make a crate to reflect the release. I am happy to do the work, I just don't know what the work is. Could you let me know what is needed?
hi. sorry for the late reply. To upload a new version to crates.io:
cargo publish
I may also need to add your account to crates.io an maintainer.
The build logic of cc/cmake has been coupling together. I am working on implementing a separate snmalloc-src crate following the practice of https://crates.io/crates/openssl-src.
But I think it is good to do a version bump first with current code base.
Sent from ProtonMail mobile
I've created an account on crates.io linked to my GitHub profile.
hi, I have sent the invitation.
Sent from ProtonMail mobile
Thanks, could you also add me to snmalloc-sys?
Sure. added!
Awesome, I published it. Hopefully I didn't mess anything up.
@licenser interested in trying 0.3.0. It might use a little less memory and go a bit faster ;)
Absolutely :D, this is exciting! The testing is fully automated now https://github.com/tremor-rs/tremor-runtime/pull/1708 is relevant PR (thanks dependabot!) and once it's merged the benchmarks are automatically published
@Licenser looks like it didn't affect your use case.
Ja not much showed up in the benchmarks @mfelsche wanted to do some additional benchmarks perhaps we learn a bit more there.
This is all in the package.
@mjp41 sorry for not catching up with upstream for a while. so do we need to remove
cache-friendly
flag now?