CaptDave
Posts: 659
Joined: 6/21/2002 From: Federal Way, WA Status: offline
|
quote:
ORIGINAL: floydg quote:
ORIGINAL: CaptDave My problem is very similar to what Grotius reported in post #1213, and a bit similar to Castor Troy's report in post #1385. Here's the scoop: Because I don't read the forums every day (some of us do have a life outside of WITP and AE!), I was humming along blissfully with v1.2 of AE Tracker. Saw my problem had been resolved, so upgraded to v1.5.1. Deleted the old data bases since my game was so old I might as well start over, anyway. The initial load of Tracker took a long time, but I chalked that up to initializing the data base (although it said the files loaded in 39 seconds). Then, after one turn, I tried to open Tracker again. Took forever, so I ended up canceling via Task Manager. Tried again the next day. First shut off the wireless, then closed down Zone Alarm. Tracker was the only application left running that I could really do anything about. Again, database files loaded in 39 seconds, but almost 10 minutes more before the application opened. I did have Task Manager open, and found that by opening Tracker my page file had soared from 165MB to 940MB, although Java was using about 24MB of RAM (with occasional spikes as high as 100MB, but generally under 50MB). This really doesn't seem normal. The large database theory shouldn't apply, since it had only one turn stored in it. Machine specs are XP w/ SP 3, 512MB RAM, severely fragmented hard drive. I'll be doing a defrag and testing the physical memory, but wanted to supply these details in case anyone has any insight. For the record, I do realize that with AE (and probably Tracker) 512MB of RAM is barely enough. I never open the two of them together, and close down everything else (except ZA, if I still have the wireless on) to run them. Until I can get more RAM, though, this is the way it'll have to be. The major change is the addition of the map. This is a real memory hog, so it could be the major culprit. Or something else could be happening... Once the tables are loaded from the database, the data is built for presentation, which requires a bit of additional processing. Maybe something is amiss there. I'd need to do a bit more profiling of where the processing killer really is. Let me know if I can provide any more help.
|