Here is my -winfo dump:
Disabling the -w option resulted in no record of progress, but did not produce any results.
Code:
Kangaroo v1.5
Loading: save28.work
Version : 0
DP bits : 28
Start : 2000000000000000000000000000
Stop : 3FFFFFFFFFFFFFFFFFFFFFFFFFFF
Key : 0309976BA5570966BF889196B7FDF5A0F9A1E9AB340556EC29F8BB60599616167D
Count : 0 2^-inf
Time : 00s
DP Size : 4872.4/6097.0MB
DP Count : 159593967 2^27.250
HT Max : 729 [@ 011F52]
HT Min : 497 [@ 0287B2]
HT Avg : 608.80
HT SDev : 24.65
Kangaroos : 0 2^-inf
Disabling the -w option resulted in no record of progress, but did not produce any results.
Why don't you just start a new save work file, so it doesn't take so long to save/read/rewrite to, and then just merge your work files?? This is your best option.
I don't quite understand ...
A total of ~ 90 separate operating systems are working on the solution and they are all connected to one server, whose progress record is set to 5 minutes.
In the current phase:
- The file with saved progress takes 5GB
- Reading / reading the progress file takes ~ 30 seconds, or a total of one minute
- The running server restarts at random times within 3-15 minutes
I don't know where in my case the best option are any combinations with joining files?
P.S. It just enlightened me :-) - is this problem also on LINUX?
Maybe I'm not following you. Earlier you said you had file saving every 10 minutes and server restart below that. So that made since why your work file was not growing with saved DPs. 1 minute read/write is a lot when you are getting higher up. If you start a new save file, reduce the read/write to 0s, you are getting more work done. Example, if you are saving every 5 minutes, and it takes 1 minute to read/write then you are losing 12 minutes of work time every hour, as opposed to less than a minute with a smaller work file. I don't know. Again, maybe I'm not tracking.
Also, if your server restarts every 3-15 minutes, who's to say it doesn't restart just prior to it saving?
