Question: state of 3.0 / 3.1 branches

[mrbean-bremen]

Background: We are using mimalloc 2 for some time under Windows, and it works great, except for a problem with large memory allocations after version 2.1.7. This may have been by design, and is not the issue here - but the problem is gone in the dev3 branch, so we want to switch to version 3 ASAP.

Question: There are the 3.0 and 3.1 branches, both are actively developed, and the release notes indicate that 3.1.5 is still beta, while there are no release notes for 3.0.10 (the last ones are for 3.0.3, which also stated it as beta). The question is: is the 3.0 branch the stable (or LTS) branch? What is it's state, it is still considered beta? What is the difference between the 3.0 and 3.1 releases, and which one is better suited for production?

Thanks!

(creating a question issue, as there are no discussions available)

[malkia]

We've been using dev3 branch for the last month or so without issues.

[daanx]

Apologies for the late reply -- the latest dev3 is in a very good state and marking it "beta" is perhaps a bit too conservative as it has been running 24/7 on some very large services for months now. I will do a fresh release hopefully later this week and mark it as non-beta. (Do not use the the 3.0.x versions -- those are internal only).

• dev1 = v1 : legacy (but still maintained as some large services rely on it)
• dev2 = v2: still the main stable version
• dev3 = v3: the latest greatest -- and it does much better for certain large workloads, especially with regard to memory footprint as it shares memory more effectively between threads.

[mrbean-bremen]

Thank you - that explains it nicely!

[mat-gas]

hi @daanx , so the 3.1.6 will be the first non-beta of the v3 releases? any major changelog compared to 3.1.5?