Code center > Suggestions

DB ate my Hard Drive!

(1/3) > >>

bacillus:
In a spring cleaning of my system, I found out that the DB folder, which I had previously assumed to be of negligible size, had eaten up 2GB of my hard drive! Deleting and zipping simulations cut this down to about 35MB, but still raises an issue. Is there any way to save simulations so they don't take up a huge amount of space? I ask as it strikes me as some part of the original spaghetti code that nobody's been willing to touch for years. (And I won't blame you for avoiding it   )

Numsgil:
Yes, we could include something that zipped the simulations before saving them to disk.  It would probably make saving faster as well, since usually zipping is faster bytes/sec-wise than disk access.  But we'd need to find some way to hook our VB6 code in to a compression library, which isn't trivial.

bacillus:
I was thinking more in the direction of saving simulation parameters seperately as they usually stay the same between saves and things like that, but sure, whatever works...

Numsgil:
It's the DNA and mutation details that take up most of the space.  The simulation details are like 512 byes, if that.

bacillus:

--- Quote from: Numsgil ---It's the DNA and mutation details that take up most of the space.  The simulation details are like 512 byes, if that.
--- End quote ---

Maybe making the mutation details optional, then? After a few dozen generations, they are usually too hard to keep track of anyway.

Navigation

[0] Message Index

[#] Next page