Endpoint Protection

 View Only

  • 1.  is there any better way to capture the i/o history?

    Posted Mar 25, 2014 10:58 PM

    Hi all, I really don't like to see that each time SEP is pointed to be the killer of system performance slow

    there should be another or a lot of killer than SEP always but it's hard to proof who are the killer at last.

    Process Monitor is good but it can't show the detail history that process/thread hiden in "System" process

    Task Manager/Process Explorer/Process Hacker shows the I/O amount of each process simply and there's only total amount but no history.

    BSOD memory dump is not yet tried, but ppl don't like to see their computer be forced in BSOD status, it's hard to get.

    is there any tool or solution better for this job?

    thanks!



  • 2.  RE: is there any better way to capture the i/o history?

    Posted Mar 25, 2014 11:07 PM
    You can try windows performance monitor. When is performance bad? During scans, updates, etc?


  • 3.  RE: is there any better way to capture the i/o history?

    Posted Mar 26, 2014 06:18 AM

    I wouldn't even bother with any of that.  Simple uninstall SEP to get a baseline on performance.  Normal day-to-day performance.  Then get a baseline during SEP's updating, scanning, etc. Compare them both.  You then don't need a history