When I hit g in the game to view the fig list, attac takes forever to save the data. I'm not sure if its just taking a long time because maybe its writing to disk every time a new fig shows up or what, but all I know is that it goes so slow that while the fig list is coming up, it jumps like crazy. I am using a cable modem with an AMD Athlon 1.7ghz processor. And twx seems to read the data just fine, and just as quick as its displayed. (ie. if I turn off the helper parses data, it speeds up at least 10x faster). Any ideas?

(I currently have figs in about 78% of a 20k size universe, for your information).

If you have any further questions, don't hesitate to either email me or post on here.

Also, when loading CIM data, it also seems to lag a bit. And it seems my hd seems to correspond with the pauses in the CIM data. Maybe you should have it instead store the data into memory, and then write it out when its done?
Maybe that would save some of the lag. Or even perhaps fork() the save process out of the main process. (Not really sure if you can do that in windows, but I remember using that option when I had to do take care of a lot of data that would freeze my program when I used to write unix-based programs)

I will look into these issues. With regards to CIM processing. ATTAC parses it as it comes off the data stream directly. it is inefficient to save it to disk and then parse it. ATTAC v3.1.1 worked like this.
Also, with regards to forking data... that is for unix. ATTAC does have 2 seperate parsing threads (like fork) so the parsing is done outside the main thread.
earth.