Dual Xeons - a processing platform I am playing with

[Camelopardalis (Dunk)]

Maybe Win11 forces all the speculative execution mitigations that the Intel chips have, and Win10 doesn’t? Just guessing, but it’s the kind of scenario where you would feel the impact.

Dual booting Linux is easy, it’ll setup the bootloader when it’s done.

[Camelopardalis (Dunk)]

Originally Posted by rustigsmed

… 3rd fastest machine on the current benchmark. although realistically i don't intend on running the PBO function 24/7 which impacts the score somewhat.

Why would you disable PBO?

[g__day (Matthew)]

I wanted to see if Windows 11 Pro offers a discernible upgrade to Windows 10 Pro performance (but it seems a severe downgrade so far).

I thought I would try Win 11 first and then tri-boot to Ubuntu next.

For me it was 80% about seeking more performance and 20% having a fallback if PI on Windows 10 Pro stops doing what it is supposed to!

Nice performance by the way

[g__day (Matthew)]

Well this is totally unexpected by me - I ran WBPP in High Quality mode against 437 subs I captured of NGC 6537 last year that I had yet to process.

I ran it twice on Windows 10 Pro and twice on Windows 11 Pro.

PixInsight's WBPP stacking at high quality - Windows 11 Pro is 3.5 times faster than Windows 10 Pro!

Windows 11 Pro took 46 minutes vs WIndows 10 Pro 2 hours and 36 mins!

LN reference generation took around 60 secs in Win 11 and 17 minutes in Win 10

Local Normalisation was similarily much, much faster in Win11.

So for WBPP I think I will be booting into Win11 henceforth!

Note that for general post stacking processing - Windows 10 Pro seems to be about 30% faster under Windows 10 Pro!

PS

Just re-processed NGC 6744 - WBPP on High Quality settings took 3 hrs 6 mins originally on Windows 10 Pro; on Windows 11 Pro - 56 mins - very, very nice performance boost!

[rustigsmed (Russell)]

Originally Posted by g__day

Well this is totally unexpected by me - I ran WBPP in High Quality mode against 437 subs I captured of NGC 6537 last year that I had yet to process.

I ran it twice on Windows 10 Pro and twice on Windows 11 Pro.

PixInsight's WBPP stacking at high quality - Windows 11 Pro is 3.5 times faster than Windows 10 Pro!

Windows 11 Pro took 46 minutes vs WIndows 10 Pro 2 hours and 36 mins!

LN reference generation took around 60 secs in Win 11 and 17 minutes in Win 10

Local Normalisation was similarily much, much faster in Win11.

So for WBPP I think I will be booting into Win11 henceforth!

Note that for general post stacking processing - Windows 10 Pro seems to be about 30% faster under Windows 10 Pro!

PS

Just re-processed NGC 6744 - WBPP on High Quality settings took 3 hrs 6 mins originally on Windows 10 Pro; on Windows 11 Pro - 56 mins - very, very nice performance boost!

nice improvement!! (still aren't you curious on what it might be on linux??

[g__day (Matthew)]

I certainly do - whilst I expect Ubuntu to be discernibly faster overall - noting the PI benchmarks often show a 60% - 100% improvement under Linux - WBPP is a bit of a surprise beast - I remember a user with a very high core count system (close to 100 cores) found Windows was the fastest for WBPP - which seems totally unexpected and wrong to me.

I seriously think PixInsight team should pay more care with benchmarks - and organise them by operating system variant and have a benchmark for WBPP too. The Benchmarks as I have said over and over on their forums can tell you if something fundamental is going wrong - but generally Jaun and team tend not to pick this priority - as users are always clamouring for more and improved functionality. My view is you have to keep quality of product high too - else tech debt looms and sooner or later everyone will have to pay the price...

Eventually I do plan to benchmark it - the only real way to know performance is to throw a real stacking workload and trying it across all operating systems!

I would love to be able to review the Thread Optimsiation data file - to see if Windows 10 Pro has different settings under Windows 10 Pro.

If it were easy I could take the Win 11 settings and try it in the Win 10 system - and see if that is better or worse - and the same for Win 10.

I still ponder the Thread Optimsation logic may get the logical core count wrong under Windows 10 in some use cases!