> I actually forgot all about this feature, which I added years ago, > long before scripts. But I may play around with performance testing > what happens if it is turned off when running a looping script. >
I got a surprise here. I found that with the automatic memory minimization turned off, a cpu-bound script ran 30 times faster (it had a long-running for loop and no i/o)! So I have changed the default way PowerPro does memory minimization in a PowerPro with exe version 4.7c I have uploaded to replace the standard 4.7 install package accessible from the webeddie web page. I added the command exec.setautominmemory (must use . form). It controls how PowerPro automatically sets its working set using the Windows API SetProcessWorkingSetSize. Call as exec.setautominmemory (interval, minmemory, maxmemory). Set "interval" to 1 to set about one second after any command, to 0 to never set, and to -1 to set with each command. Set minmemory and maxmemory to memory sizes in bytes; see description of SetProcessWorkingSetSize at MS site for more information. PowerPro starts with exec.setautominmemory(1,-1,- 1), which means that memory is only mimimized about 1 second after each command. Use exec.setautominmemory(-1,-1,-1) for previous behaviour, and exec.setautominmemory(0,0,0) to disable. This version also includes the fix for the wrong showing of hidden windows.
