Pending reboot

[spiff_21]

If you show the column “Pending Reboot” and have many server (20+) The program starts to get extremely slow.

[doug]

Hi spiff-21 – Thank you for the feedback. Can you please describe in more detail what you mean when you say “the program starts to get extremely slow.” Are you saying that the check for pending reboot takes time to complete on many computers? Or are you saying that after the check has completed, if the column is visible, then when you scroll in grid or select rows etc that it doesn’t scroll quickly or select quickly? Something else? The more descriptive you can be, the better.

Thanks!

-Doug

[StefanE]

Hi,

I can confirm this behaviour. I faced performance issues since weeks with BatchPatch (GUI slow response, high CPU usage). This forum discussion here give me the idea what is the reason for it.

I can reproduce it like this:

Add “only” 20 servers to list. Start pinging all. Everything still fast. If you click any row everything reacts fast (Clicking any grid row results in fast selection of the grid row – if you click another this is also selected/highlighted fast). Start checking for updates. It gets little slower, but this is acceptable. Starting to query the pednig reboot status. Column “Pending Reboot” is now visible. If you now click any grid row it is slow. Until the grid row gets selected / highlighted it takes sometimes seconds. The CPU usage increases while clicking around. If you hide the row it is fast again. It looks like it is also fast if you make the batchpatch window smal and the column “Pending Reboot” is not shown (need to scroll right).

Hope this will be fixed soon!

Regards,

Stefan

[StefanE]

additionally only the rows are “slow” that have entries in the Column “Pending Reboot”. If you are clicking around in other “empty” “Pending Reboot” rows it is fast.

[doug]

Thanks, Stefan. We understand the cause of this behavior, and we should be able to have it fixed for next release.

-Doug

[Author]

Posts