mimalloc VS GLM

mimalloc: mimalloc is an open source implementation of malloc, currently the best performing allocator.

Some compiler writers thought that was the case, if [0] is related to OP. I don't have a "modern" (after 6th gen) Intel CPU to test it on, but note that most programs are compiled for a relatively generic CPU.

[0]: https://github.com/microsoft/mimalloc/issues/807

Yes, it's very efficient and that's not where the main problem lies. However, small allocations with modern C heap allocators like mimalloc or snmalloc has gotten extremely efficient as well. Would be interesting to see a benchmark comparison with Java's G1 and ZGC.

Memory management for C is not itself a solved problem, not only is there a lot of performance to squeeze out of malloc itself (the benchmarks on https://github.com/microsoft/mimalloc exemplifies the variance between the implementations), but it's up to the programmer to implement memory management in the large in an efficient way, which is not an easy task. One sure mark of a slow C program is one with a ton of mallocs and frees strewn all over.

It's a very terse howto for replacing Factorio's memory allocator with Microsoft's mimalloc, and configuring mimalloc so that memory is always allocated on huge pages by using madvise().

I was wondering if Koka's perceus referencing counting style is any different from the reference counting that Lean4 implements? I understand that both rely upon the mimalloc (https://github.com/microsoft/mimalloc) library in the backend.

If you are fine with heap allocations then there are only few dozens operator new/delete to override to regain control over normal C++ code memory use. Allocators and STL all need to call those. At least that's what gaming does on all platforms. If you need examples you can check Mimalloc on github ( https://github.com/microsoft/mimalloc/blob/master/include/mimalloc-new-delete.h ).

What's the difference between this and Microsoft's? https://github.com/microsoft/mimalloc

Version 0.1.31 of the Rust wrapper for the mimalloc memory allocator has just been released!

I am a greenhorn at graphics programming. I just made an app in OpenGL with C++ that I now need to change over to a browser app with WebGL. WebGL looks pretty cool but since my app does a lot of calculations I assumed I should keep the heavier calculating parts in C++ with emscripten ( which I am also just learning ). So looking at it, it just looks like glm is the only library I seriously need for my c++ code and that seems pretty cool because it is a header only app it says. But in the github there are a lot of folders and files so I am not sure which are indispensable or not. Any advice?

GLM does it quite well, it has core includes then a detail folder with all the inl files that get added. https://github.com/g-truc/glm

I once ported an OpenGL code base over to Metal. For me, it was essential to do as much code sharing as possible. Because I was using the GLM library in that code base and generally found that library very useful I wanted to know whether I can use GLM with Metal. I had to do some research but it turned out it works really well, see here

I would also recommend GLM

Alongside MiniEngine, you’ll want to look into the DirectX Toolkit. This is a set of utilities by Microsoft that simplify graphics and game development. It contains libraries like DirectXMesh for parsing and optimizing meshes for DX12, or DirectXMath which handles 3D math operations like the OpenGL library glm. It also has utilities for gamepad input or sprite fonts. You can see a list of the headers here to get an idea of the features. You’ll definitely want to include this in your project if you don’t want to think about a lot of these solved problems (and don’t have to worry about cross-platform support).