alex 537 8.5 -25.0 549672 524864 ?? R 1:48PM 0:16.28 /usr/bin/perl -I/Applications/TextMate.app/Contents/SharedSupp
alex 509 0.4 -36.9 1042488 774576 ?? S 1:45PM 0:36.49 /usr/bin/perl -I/Applications/TextMate.app/Contents/SharedSupp
So this is actually kind of funny. Perl was dutifully creating objects, when all of a sudden, it runs out of memory. Oh noes, here comes the swap. So it alternated between using 100% cpu and swapping the shit out of my disk. Darwin, for those of you who do not know, allocates swap as it goes along. In this case, it was seven gigs. This is a laptop, and I have two gigs of ram, but I do not have endless quantities of disk from which to pull swap.
Anyhow, I think the fourth column is the most interesting in this example.
I remember when I worked at AOL, I had data structures that were too big to fit into memory, and I can't for the life of me remember how I got around the "2gb series" limit. If you serialize to disk, that's just as bad as swapping.
So I guess I'm just going to kind of sit on TDMA until I figure out how to get around the fact that you can't approach it a whole day at a time, and I don't know how I'd keep sync between new instantiations (the military use dedicated time boxes).