Change our no_std allocator #343

Activity

1. github-actions

   added

   lifecycle/needs-reviewThe issue has not yet been reviewed.The issue has not yet been reviewed.

   on Mar 11, 2025
2. prydt commented on Apr 4, 2025

   

   prydt

   on Apr 4, 2025

   Contributor

   More actions

   Hi, I was wondering if I could take this issue.

   If so, I was wondering if there are any good benchmarks for hyperlight I should use to compare different allocators.
3. danbugs

   added

   lifecycle/confirmedBug is verified or proposal seems reasonableBug is verified or proposal seems reasonable

   and removed

   lifecycle/needs-reviewThe issue has not yet been reviewed.The issue has not yet been reviewed.

   on Apr 23, 2025
4. danbugs

   added the

   Enhancement

   issue type on Apr 23, 2025
5. danbugs

   modified the milestones: v0.4.0, v0.5.0 on Apr 23, 2025
6. danbugs

   added this to Hyperlight Milestoneson Apr 23, 2025
7. danbugs

   modified the milestones: v0.5.0, v0.6.0 on May 21, 2025
8. danbugs

   modified the milestones: v0.6.0, v0.7.0, Upcoming on Jun 4, 2025
9. jsturtevant

   modified the milestones: Upcoming, Backlog on Jul 2, 2025
10. jsturtevant commented on Aug 26, 2025

    

    jsturtevant

    on Aug 26, 2025

    Contributor

    More actions

    mimalloc (if possible?)

    Just noting that there was a brief investigation into mimalloc and it was found that it needed 64Mb of memory for the initial arena which ruled it out. Not sure if that is still the case.