O outro dia eu estava jogando ao redor com Opções da execução da lima da imagem e Sysinternals' Monitor Process, em Vista. Eu vi uma pergunta interessante ocorrer. Usando notepad.exe como um exemplo, eu vi uma pergunta para uma chave chamada “PerfOptions” em [HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ opções da execução lima da imagem \ notepad.exe] quando eu funcionei o notepad. O resultado era NÃO ENCONTRADO CONHECIDO, assim que eu decidi-me retificar aquele. Após ter adicionado uma chave nomeada “PerfOptions”, eu funcionei o notepad outra vez. No monitor Process, eu vi perguntas para quatro valores:

• IoPriority
• PagePriority
• CpuPriorityClass
• WorkingSetLimitInKB

Por causa das explorações recentes com priorities* process, CpuPriorityClass agarrou-me direito - afastado. Olhar SetPriorityClass a função, uma pode ver os valores diferentes para o parâmetro dos dwPriorityClass. Eu criei um CpuPriorityClass nomeado REG_DWORD em PerfOptions, e ajustei o valor a 0×80 nas esperanças que o notepad lançaria com o “HIGH_PRIORITY_CLASS”. Instead, lançou-se com uma prioridade de NORMAL_PRIORITY_CLASS (8) - que o ajuste não tinha feito algum impacto. Então, eu ajustei o valor a 8 e lancei o notepad. Notepad lançado com uma prioridade de 8. Eu mudei o valor a 4, e aquele não teve nenhum impacto. Eu mudei o valor a 0 - nenhum impacto. Eu tentei 10 - nenhum impacto. Eu não poderia ver alguns

…

Cada uma vez em um quando você observa que sua movimentação dura está trabalhando extremamente duramente para o que parece como nenhuma razão. Um processo de fundo fêz exame de seu refém da movimentação dura, forçando o para debulhar alta enquanto se esforça para proseguir com a taxa elevada de lê e escreve. Seu computador responde lentamente enquanto o processo sobrecarrega as limitações físicas de sua movimentação. Que é você a fazer?

A solução é simples, embora um pouco complicado às vezes: identifique e pare o processo que está matando sua movimentação. There are two methods and tools that you can use to identify the process. (more…)

computer, disk operations, download process explorer, down arrow, Drivers, explorer 2, Hardware, hard drive, hostage, menubar, performance tab, processes, reliability, responds, struggles, sysinternals

Previously (Part 1: Introduction - What's using my CPU?), I kicked off what I expect to be a multi-part series on determining what is causing excessive CPU consumption, outside of the normal "which process has the highest value in the CPU column in Task Manager".

Before I get into things, a little bit of background may prove useful or mildly entertaining. Over on "Sysinternals Forums", there were recently two similar problems that both involved excessive CPU utilization that was not attributable to a specific process. I became involved in both problems and attempted to use similar techniques to get additional information with the hopes of ultimately being able to pinpoint the problem. What may make this mildly entertaining is that in both cases, there was limited or no success in detetmining the cause of or solution to the problem. In the end, one problem was resolved by disabling the floppy disk controller, and the other problem appears to be as of yet unresolved. (In the latter case, the poster did admit that the system was experiencing hardware problems - the chipset fan was dying and there...

Recently, I have been involved in attempting to diagnose problems with excessive CPU utilization. Often times, this type of thing is relatively easy to identify - at least as far as pointing the finger at the thing that is consuming CPU cycles. Task Manager can be used for this - simply sort the "CPU" column in descending order and note the process that is at the top of the list. One can use a similar technique with Process Explorer.

In the past (here and here), I've given examples that demonstrate various techniques that can be used to try to determine what a process is doing when it is consuming so much CPU. Sometimes, you can do something about it - if you have the debugging symbols, perhaps there is something in the stack of the thread or threads in the process that is consuming the CPU that will lead you to some setting, feature, or configuration piece that can be manipulated so as to avoid the problem. Or perhaps just knowing the module name is enough information to identify the problem software - a recently installed add-in / plug-in, or a new utility,...

I've written about Sysinternals' Process Monitor utility before:

• Microsoft / Sysinternals Process Monitor
• Using Process Monitor to Troubleshoot Internet Explorer 7 Performance Issues

I have had a few months now to work with Process Monitor, and it certainly is amazing. The filtering capabilities are great, and the fact that the filters are not destructive makes slicing and dicing the data many ways quite simple. The ability to capture all of the data that the utility can capture makes it quite powerful, and the ability to get stack traces for each event is extremely useful.

Going off the observation that Process Monitor is currently at version 1.01, and the assumption that the utility will see further development, I have hopes that the following relatively small ideas will be taken into consideration for future releases, and that further discussion and conversation is sparked.

1) Allow for the use of CTRL+C to copy selected data to the clipboard. Some data can be copied in this fashion, but from my experience not much. In many cases, one can right-click and choose "Copy" from the context menu, but that's inconvenient. For example, on Event properties, on the Event...