R
Rein Petersen
Is there any way to adjust thread priority for the garbage collector?
Would be nice if I could tune the thread priority rules for the garbage
collector too...
From my readings of the process, when memory becomes limited, the garbage
collector is moved up in priority. I believe they must be overly simplified
explanations because I would tend to guess that Microsoft would have allowed
for more pre-emptive reclaiming of memory to best gracefully degrade (share)
performance. The few simple benchmark tests have led me to that conclusion
anyway.
Still, I wonder if MS can really dynamically tune their garbage collector
for all occassions or if we are better off making our own fine tunings. I
only find the ability to manage assemblies, security policy, and remoting.
Ideally, Local Machine Settings for garbage collection tuning could be
protected from override in software settings using security policy.
Can anyone refer me to text on the subject (if it exists)?
Rein
Would be nice if I could tune the thread priority rules for the garbage
collector too...
From my readings of the process, when memory becomes limited, the garbage
collector is moved up in priority. I believe they must be overly simplified
explanations because I would tend to guess that Microsoft would have allowed
for more pre-emptive reclaiming of memory to best gracefully degrade (share)
performance. The few simple benchmark tests have led me to that conclusion
anyway.
Still, I wonder if MS can really dynamically tune their garbage collector
for all occassions or if we are better off making our own fine tunings. I
only find the ability to manage assemblies, security policy, and remoting.
Ideally, Local Machine Settings for garbage collection tuning could be
protected from override in software settings using security policy.
Can anyone refer me to text on the subject (if it exists)?
Rein