Maybe Cloudflare’s pingora suits this purpose better given that it is being used by cloudflare to proxy traffic at a large scale
Check out my blog: https://nereux.blog
Maybe Cloudflare’s pingora suits this purpose better given that it is being used by cloudflare to proxy traffic at a large scale
Yeah that just wastes both people’s time
Yeah that’s the fun part!
Maybe there are also some security implications of the code?
Because the thing is: That code is probably gonna end up in production somewhere
Hmm now it would be interesting how eyra fares for allocating. And also why does musl not implement a faster allocator? I get that it should be backwards compatible but the gap to glibc seems to be really large.
This is my first post on the Threadiverse! I hope i didn’t miss tagging the post with a flair. If you have any feedback feel free to write in this thread!
This is a smaller blogpost but i will write larger ones in the future hopefully more in-depth than those in the past
A general purpose memory allocator although this is really much a work in progress i think there are some good opportunities for otimization in a memory allocator for rust.
For example Rust gives you the size of memory region to free, which means the allocator does not have to track that.