Some software programs can be optimized to startup faster which might be the appropriate thing to do if they are used regularly by the user. One prime example would be to disable Java in Open Office which speeds up the application at startup quite a bit. It sometimes might be obvious that an application is starting up faster but it is always better to get solid proof.
Application Startup Timer (via How To Geek) can deliver that proof by measuring the startup time of applications. The application opens and closes a a selected application and logs the startup time of the application in a log file. This provides information about the performance gains when run before and after optimizing an application.
The application’s interface requires some explanation. The first field named Application has to point to an application on the system. The second called Cmd Line is optional and can be used to execute command line parameters. Log File points to a log file on the computer’s hard drive while Window Name has to contain part of the window’s name so that the application startup timer can automatically close the window.
The first three check boxes determine how the application is detecting the window of the application that is currently tested while the last three check boxes determine how the benchmarking software should close the application window. The values shown in the screenshot should work fine for most applications.
Related posts:
Timer ApplicationDelay Windows Startup to Speed Up Startup
Windows Timer
Windows Boot Timer
Windows Timer
Delay Startup Software
Windows Startup Speed Benchmark
Application Monitor
2 Responses to “Application Startup Timer”
Trackbacks/Pingbacks
-
[...] Some software programs can be optimized to startup faster which might be the appropriate thing to do if they are used regularly by the user. One prime example would be to disable Java in Open Office which speeds up the application at startup quite a bit. It sometimes might be obvious that an application is [...] Read More [...]
On linux you might want to use the “time” command to do the same – just “time applicationname” and see the stats.