Investigate qimalloc as a replacement for wee_alloc

[MaksymZavershynskyi]

Currently we are using wee_alloc for Rust contracts and contracts used in benchmarking. https://github.com/wasmx/qimalloc is used by EWASM and might be potentially faster than the default wee_alloc, since qimalloc optimizes for speed and wee_alloc optimizes for code size. qimalloc however gives only 2-3kb overhead compared to wee_alloc, and in our case using qimalloc might increase the TPS which is more important.

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

[bowenwang1996]

@mikedotexe please check whether this is still relevant

[nagisa]

https://crates.io/crates/rlsf is an option to consider. Since WASM code is always single-threaded, concerns about this allocator requiring locks for concurrent use are irrelevant.

[robdefeo]

From my dependancy bot alert, it is still relevant to replace wee_alloc

Two of the maintainers have indicated that the crate may not be maintained.

The crate has open issues including memory leaks and may not be suitable for production use.

It may be best to switch to the default Rust standard allocator on wasm32 targets.

Last release seems to have been three years ago.