I am testing microsofts .net runtime optimization tool for ASP.NET 2.0 on win13, it runs as a low priority background task, but consumes a bit of cpu in this process. The CPU usage is a bit higher than normal, but being that it is a low priority task it does not prevent other processes from utilizing the cpu.
So if cpu usage is a bit higher today, this is the reason now, as I am testing this tool. Earlier in the day there was actually a problem with a php based site consuming a lot of the cpu, but this was resolved and I started the .net optimizer about an hour after that resolution.
I will be keeping a close eye on the server throughout the day with the optimizer running, as it does make tracking any hanging pages, bad, code, or abuse harder to find since it has an artificially high cpu use in place.
I am hoping this tool will help with the asp.net 2 page load compiles significantly.
So if cpu usage is a bit higher today, this is the reason now, as I am testing this tool. Earlier in the day there was actually a problem with a php based site consuming a lot of the cpu, but this was resolved and I started the .net optimizer about an hour after that resolution.
I will be keeping a close eye on the server throughout the day with the optimizer running, as it does make tracking any hanging pages, bad, code, or abuse harder to find since it has an artificially high cpu use in place.
I am hoping this tool will help with the asp.net 2 page load compiles significantly.