- explicit disable all CPU extensions except SSE1
This means that Spring will not use many optimizations? Sounds sad.
Else it won't sync in online gaming ...
Before it just set march=i686 & relied on gcc not enabling such extensions and in case of linux 64bit compiles it was a very optimistic `hope` that it will sync (some march's strangely did, with other it didn't).
- on multicore systems set scheduler to SCHED_BATCH (semi-solves the core hoping issue)
What is it? Linux distribs will have this option disabled by default? This means that it's better to compile spring from sources?
It doesn't tell anything about distros.
And @what it is, it's a different thread scheduler (how the kernel distribute cpu time for the thread). Also it is something like a `hack`, SCHED_BATCH is by design _slower_, but in case of a 100% cpu usage thread & free cores it will be _faster_ cause it won't shuffle the thread across the CPUs anymore. I detected >>10core switches per second, also none core was ever running at full speed cause this way they were never running at 80% usage. It's a very critical _bug_ in the linux kernel (or I am just running it with wrong param?), and I would really like to speak about this with a linux kernel dev some time.
I think this change needs more detailed description:
- improved behaviour of builder masses
sounds interesting but I can't understand what it means
It's how builders check if their building was already started (and finished) by another unit, before they always travelled to the buildpos and then checked if the job was already done. Now they already check on their way if it is done.