In order to perform a search or to fetch or process tags, the client has to interact with these files in many small bursts, which means it is best if these files are on a drive with low latency. Depending on the size of your client, these might total 1MB in size or be as much as 10GB.

The client stores all its preferences and current state and knowledge about files-like file size and resolution, tags, ratings, inbox status, and so on and on-in a handful of SQLite database files, defaulting to install_dir/db. If you run it without command-line parameters, it will try to write to its own directory (to create the initial database), so if you mean to run it like that, it should not be in a protected place like Program Files. An SSD will load it marginally quicker the first time, but you probably won't notice. It doesn't really matter where you put this. If it sees a database running at a lower version than itself, it will update the database before booting it. If you just run the hydrus_client executable straight, it looks in its 'db' subdirectory for a database, and if one is not found, it creates a new one. It doesn't store any of your settings-it just knows how to present a database as a nice application. This is the part that comes with the installer or extract release, with the executable and dlls and a handful of resource folders. This document will update to reflect those changes! database migration ¶ the hydrus database ¶Ī hydrus client consists of three components: I am working on this system right now and will be moving the 'move files now' action to a more granular, always-on background migration. Informing the software that the SQLite database is not in the default location

These components can be put on different drives

Hydrus Network 546 for mac download