UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Why is APP counting 28 Threads with 28 CPUs? Hyperthreading enabled. I uses only half of the logical cores.
Windows 10 Pro.
I had a similar problem with AMD EPYC, 64 CPUs and only 64 Threads, same OS.
But on another Machine with 16 CPUs it shows 32 Threads. Same OS.
What is going on?
It seems I found a solution on this particular machine:
In the BIOS-options there was an entry for NUMA. I set this from "clustered" to "flat".
Now APP can see all logic cores and uses 56 threads.
But there is something I mentioned in summer that needs to be solved:
In Windows 10 I can use all threads in APP until the final Integration-task starts. There I have to step down to max. 32 threads, otherwise APP crashes with a Java-error if more than 32 threads are in use. This only seems to accure with my big 190-tile mosaic.
