What? Did I leave that out? oops... OK.

In the inefficient scenario that's 10 fields of 4 double precision numbers: total 40 bytes. 100,000 events = 4 million bytes.

In my scenario that's one double precision for Julian date (4 bytes), 4 single precision for lat, long, depth, mag (2 bytes each): total 12 bytes. 100,000 events = 1.2 million bytes. A savings of 70%.

Even so, I can't figure how he eats up 1.5 gigs of memory to do this. Right now my computer is using 1.37 gigs of ram. I have two Firefox windows open with dozens of tabs between them, email, usenet client, 3 text files, paint shop pro, 2 instance of XBasic, an image browser, and I'm running another test render of my animation. Oh, and Seti@Home is merrily crunching away in the background as well.

Brian