Not logged inRybka Chess Community Forum
Up Topic Rybka Support & Discussion / Aquarium / Daily Maintenance of Aquarium
- - By ChiefPushesWood (**) Date 2018-04-19 15:20
Yesterday and today, Aquarium seems to be cooking along as I imagined a polished software would. I'd like to keep it that way. So...

What daily or weekly maintenance duties should one perform to keep it running smoothly?
I did do a search but most of the posts are on older versions and there didn't really seem to be a consensus (deleting IA files, etc)

So what say you? Maintenance anyone?

Parent - - By dickie (**) Date 2018-04-19 15:46
Daily I delete all *LOG.old files and make a backup of Aquarium\Data, though I cannot remember when I last needed help from the backup. That is enough for me.
Parent - - By ChiefPushesWood (**) Date 2018-04-19 17:04
Thanks dickie.
Parent - - By Ghengis-Kann (***) Date 2018-04-19 21:07
Daily seems a bit much, but here are a few things I do.

Automatic backup of all of my trees and tree configurations.
This is done nightly to a different hard drive from the one Aquarium is on, and I periodically delete the old backups.
Do not rely on the tree backup system that comes with Aquarium.

If you lump all of your infinite analysis into the same tree then it can become gigantic and might start to slow things down after awhile. If that happens then delete it.
Better is to have separate permanent IA trees for every project. This requires a  bit more work because you have to manually tell the IA engine or engines which tree to write to every time you switch projects, and it isn't very practical if you have multiple projects running simultaneously since each project would each need a dedicated IA engine.
The advantage is that you can add this tree to your configuration and see how deeply you have searched each position with IA. This might be doable with a single IA tree for everything, and maybe that won't cause issues with newer versions of Aquarium, but I haven't tried it.

I haven't used automatic expansion in awhile, but recall there being a tree called Deep Analysis that I used to delete when it got gigantic (like > 2 GB).

If you run remote engines they will generate useless log files that should be cleared out once in awhile because otherwise they will consume gigabytes of storage for no purpose.
Parent - By Viktor (**) Date 2018-04-20 06:10
Projects large volume of not delete. They can be used as a kind of debut book. You can also add a large number of database batches to these projects for analysis. Thus, we update the project. Periodically, these projects should be merged into the Master tree.
Up Topic Rybka Support & Discussion / Aquarium / Daily Maintenance of Aquarium

Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill