From: Bruce W. <br...@mi...> - 2000-10-06 13:14:47
|
> My system has 64,996M, I'm running mh.bat with the "test " > code and perl 5.005, which occupies 27.820M total memory. The > file cache uses 11M. With all the other programs running there > is 2M of physical memory left. The CPU usually is 87% idle. > The initial stuttering went away after I rebooted the system, but > it creeps back after running for 30 minutes or so, depending on > other program usage. Free physical memory does occasionally > drop below 1M. Pardon the expression, but I didn't realize mh > was such a memory hog. Yep, it is quite a memory hog. That is one of the tradeoffs with perl. Here is what I see with the latest code: Linux 10 Meg <- mh -tk 0 mh_control.pl (run just one code file) 12 Meg <- mh -tk 0 (run all the test code) 17 Meg <- mh ( " with tk gui on) Windows 18 Meg <- mh -tk 0 mh_control.pl (run just one code file) 20 Meg <- mh -tk 0 (run all the test code) 27 Meg <- mh ( " with tk gui on) I'm not sure if the difference between Windows and Linux is real or just in accounting. One thing to keep an eye on is to make sure we don't have any memory leaks. I have one now with one of the new things in my code that leaks about 1 meg every 3 hours. Reloading code, with the tk interface on, leaks a little each time (the tk widgets have a bug where they don't free all memory). The memory footprint has grown over the last year by about 5 meg, due to various new features. Much of the code is only loaded conditionally on use, but not all of it. We could try to do more of that. Bruce |