Timeline for How to automatically run a batch file each time an application opens in Windows 10?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25 at 22:49 | comment | added | Ben Hutchison |
Like most performance analysis it's subjective and situation-specific. Starting a new console host process isn't free, but it may not be noticeable underneath a certain frequency, especially as the CPU speed and core count increase. In the spirit of avoiding premature optimization, I would probably go with the scheduled task batch approach until it became a problem. Then I'd switch to a permanently resident background process that starts once and subscribes to Event Log, for example in a C# Windows service that uses System.Diagnostics.Eventing.Reader.EventLogWatcher.
|
|
| Apr 25 at 12:27 | comment | added | nehalchoy | I have another question. Would there be any performance penalty associated with process tracking? I fired up Event Viewer on my laptop and saw 16,000 events in the Windows Security Log after seven hours of normal usage. | |
| Apr 25 at 12:10 | vote | accept | nehalchoy | ||
| Apr 25 at 7:10 | history | answered | Ben Hutchison | CC BY-SA 4.0 |