Performance difference of the precompiled executable from github

[aannleax]

On my system, at least for the deep-100 use case, the precompiled executable from github (Version v0.1.0) is a lot slower than if I were to compile the executable myself.

Compiled v0.1.0:
Reasoning completed in 2018ms. Derived 20202 facts.
   Loading input:   1797ms
   Reasoning:        220ms

Precompiled v0.1.0:
Reasoning completed in 4122ms. Derived 20202 facts.
   Loading input:   3847ms
   Reasoning:        274ms

This needs some investigation.

[mmarx]

This is most likely because the action builds a static binary, linked against musl, whereas by default, you will get a binary that links dynamically against glibc. In particular, this means it uses another memory allocator, which might not be as efficient. Likely, the way to fix this is by replacing the action (since it doesn't support linking against glibc).

[mmarx]

We probably just want to use something like htis: https://github.com/BurntSushi/ripgrep/tree/master/.github/workflows/release.yml

[mkroetzsch]

Does this affect all binaries or just the Linux builds?

[mmarx]

Just the linux builds, but that's the only one we're building automatically anyway right now.