Quote: Originally posted by loclhero  | Does GSB do any checkpointing, where it saves intermediate results while systems are being built?
I've run into the situation a couple of times where I've lost GUI response in the morning to a Manager and Worker and so I was unable to recover the
many systems that had been created overnight.
Alternatively, I don't suppose there's any command line access to GSB that would allow me to terminate workers and managers gracefully so as to
preserve the computations they've done?
Thanks for any insights or pointers. |
Lclhero, it is possible to save systems and there are configurations to allow GSB to save systems that pass some performance filter, just as you use
to market systems for inclusion in FavA, FavB, etc. However, in my experience, I've never gone back to look at anything that is autosaved and it has a
tendency to chew up a lot of disk space. I know I and most other GSB users turn off this feature.
I think the bigger question is why you feel the GSB Manager is becoming unresponsive. I'm running GSB Manager 7 days a week and have not seen this
behavior. Also running hundreds of system building runs over the course of days and don't see this, so I would suspect some other problem that needs
to be addressed.
Your reference to Manager/Worker is also a bit confusing and I wonder if you are doing something you shouldn't or have some other expectation. Workers
are kind of transparent to the system building process. I don't ever think about the Workers and what they are doing (except in the rare case I cannot
produce systems in a build run).
I know I and others have written this several times and don't mean to harp on this but I think the best starting point for figuring out how to use GSB
is probably Peter's latest GC videos.
If the issue with losing response from Manager continues to happen, I suspect Peter will want to jump on remotely and help you figure it out.
I assume you are running on a machine with plenty of memory and cpu. |