|
|
|
This test measures the current version (v4.00.23 as of writing) to ensure there are no memory leaks or other problems. Notice the low overhead. Whether 2 days or 2 months, these graphs would look the same. The GUI main window was not visible when this snapshot was taken, though had been previously opened. Opening the main window would show a bit more resource use by the GUI (ProcessLasso.exe), but not much. Most of the time it is sitting in the system tray, and that is the metric we wanted to record in this test.
Please note that resource utilization varies from system to system depending on the software and hardware environment. The more running processes, the more memory and CPU use (but not much more). Thanks to our proprietary icon optimization technology we have reduced overhead from keeping high-resolution process icons in GUI memory, but have not eliminated the overhead all together (as it would be impossible without re-referencing the disk every time). Therefore, the process count particularly has an effect on the GUI where process icons take up memory. Still, Process Lasso is slim no matter how you cut it.
What is even better is that we are getting slimmer, not fatter. While it may be an obsessive/compulsive waste of time, I continue to fine tune both CPU and memory utilization. This is why I'm sure corporate America will never beat us, as they aren't going to invest as much time to care since it isn't 'fiscally benficial'. They will figure an extra megabyte or two of memory doesn't hurt anybody, who cares. They rarely care if their software even works (sad but true). There are LOTS of software companies out there founded by some guy who had an idea, but couldn't program it. They hire some independent contractor from one country or another, who develops some software. This software they then market the crap out of -- always more concerned with appearances than actual functionality. Of course, there are other good software companies in the world too, do not let me get you too depressed ;). My point is that it is the small developers who usually care most.
This are screenshots from Process Explorer, for the curious. It does a good job of computing what Process Lasso calls the 'private working set'. This is the amount of virtual memory that process is, all by itself, using.
Tested version: 4.00.23 x32 Workstation
Tested OS: Windows XP Professional @ SP3
Test time: 48 hours
Process Lasso is a 'resident' application, as are many others. This means it is always running (though of course the GUI can be closed entirely if you choose, leaving the core engine to do its duty). It is imperative any resident application have minimal resource utilization. Why? Simply because it is always running.