factorio-docker VS mimalloc

Luckily, some kind folks maintain container images of the Factorio headless server. This alleviated some of my maintenance woes, but at this point, why not use a modern container-based solution?

I got the new DS224+ which comes with an Intel processor so it seems like the perfect server setup. I just started looking into this but this docker image seems perfect. Now DSM has changed it's docker app name to "Container Manager" which was the first hurdle I had to get over. Now I need to figure out how to setup the config for the docker image and setup a secure server that's exposed to the outside. (I got a unifi network running.) Anyone done this yet? Any pointers?

In the end my Factorio server ended up running bare metal just because it was easier, so I might not be the right person to answer that. :) I just did https://github.com/factoriotools/factorio-docker before I tore it down, basically.

I am running a factorio server via the docker image from https://github.com/factoriotools/factorio-docker. Running the server, setting up mods and running a custom save all work fine.

There already exist Docker images for factorio servers, enabling one-click download, installation and running of a server. https://hub.docker.com/r/factoriotools/factorio

Update... I used the container found here and modified the docker-compose file to set QEMU_EXECVE=1 in the environment variables. Assuming you have the qemu-user-static package installed, this will utilize QEMU user space emulation for the container. Works fine so far, no checksum issues. No idea how fast it is though compared to box64. I'm also on the oracle cloud ARM box you have.

How long until Steam auto-updates generally? There's already a new image on factoriotools and I updated my server but haven't gotten the update on steam yet, so now they're out of sync.

And here's where the image is (with instructions and all): https://github.com/factoriotools/factorio-docker.

Switching to jemalloc or mimalloc doesn't improve the performance either.

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.