stxx
Personally.... not sure why anyone would screw with this file... Often these are parameters that are there for developers to help test, debug and tweak but usually not really for user modifications. I would be really careful as many of these parms are likely related to one another in ways users can't know because we didn't write the code. if you are having issues running sonar, I'd look elsewhere before messing with these parameters
This file is there for the User to make Advanced settings.
Every single parameter in the file should be documented and should not be screwed with but rather understood and used if necessary.
These settings are not just for the developers they are there for users to make modifications responsibly understanding the parameters beforehand.
I cant tell you how many forum posts i have gone through over and over again (" recently searching for the missing documentation" ) of users asking about certain AUD.ini settings because they have problems and no documentation "Years and Years worth", and even though a few setting may not read the code anymore, or relate to legacy products, or not suit people who do understand them, i want to know what every setting represents and i am sure you would read through that documentation to. It is important to understand all of these settings, it is important to have documentation on all of them. It is important to use them if you need to.
There is a AUD.ini "Undocumented "thread for this discussion( which seems to be in the bin at the present moment because i edited/Removed from the UNDOCUMENTED List a setting i recently found documentation on, which happens it should be back thanks to scook!).
This thread was started for "Documented "settings, it is for Advanced users to hopefully discuss a/these setting/s they adjusted that helped a problem or suited there system more, so novice users can have a better understanding of what the advance settings could help or be used for.
example :ThreadSchedulingModel=
I had this setting on the default :1, have a system with more than 4 cores and after reading the documentation i decided this could benefit me, Before rushing in i opened a big project and took note of the platinum CPU meters which looked balanced except my first core was a lot higher, i then changed this setting to 2 and instantly that first core disappeared (lower than the rest ), also the rest of the cores were more stable and even.
So :2 is my default setting for this, not the developers default:1! Now lets remember that windows operating system loves the first core, so this defiantly relates to other parameters ( windows/Sonar) in a "Good" way that we may never know exactly about, but we know its better !
Remember like a lot of things in life when you understand things they are easy and there is less frustration and you can quickly find and fall back on and change because you understand it fully, my point is it is the same with settings, when you know 1 of these settings properly/Fully then you know its there what it does and that's that, but when you don't know a setting it makes more problems than knowing.