floydg
Posts: 2052
Joined: 6/27/2004 From: Middletown, NJ Status: offline
|
quote:
ORIGINAL: fcharton Since a few turns, the time needed for Tracker to initialize underwent a noticeable change, from less than a minute, to 12-15... (840 seconds for the base load, and about a minute more for the actual program start) I now have 167 turns in the database, it is big (270MB) but not huge. During the database load, memory usage is relatively low (about 150MB), as is processor usage (a few percents) During the program load, both get slightly higher (500MB and 15-30%, on a dual core), but nothing too bad. What seems to kill the whole thing seem to be the IO, and specifically the reads : Windows records 6 million reads for the base. I suspect the speed could be nicely reduced if some of those could be cached (there probably are a few files/data structure which bear the brunt of the IO). The fact that the change happened suddenly once a certain limit is reached suggests some parameter in Java or the database... (ie over a certain size, everything is done on disk, and gets slow) In the meantime, is there any way I can speed up the loading, some way to "pack" the existing DB? some change in my java configuration? Thanks in advance. Francois Sorry, not much you can do here. I experimented a bit with some optimization with ship information. I did this several releases back and there were no complaints, so maybe it worked. That means I can apply that to some other database tables when I find some time (it's not simple).
|