![]() Use this approach if you have a collection of files that have already been indexed, and you simply want Sononym to use the existing sononym.db Scenario #1: Symlinking an existing library Other than this, there is no real advantage of using symlinks - if the media you are offloading the database to isn’t faster than the existing drive, symlinks won’t be faster as a result. Offloading the database means you can avoid “locking” issues, since each team member works on their own database. Offloading the database means that these files are created elsewhere.ĭo you want to access a shared pool of samples with other people? Offload the database to a local disk to speed up access - or use SSD for even faster access.ĭo you want to index files that are stored in a read-only location, or irked by the presence of sononym.db files in your sample collection? Offloading the database to SSD can speed up initial access dramatically, by a factor of up to 10-50x.Īre you accessing samples from a network drive (NAS, or otherwise)? ![]() How do I benefit?Īre you accessing your samples from a mechanical harddisk, but have an SSD drive with a few gigabytes of free space? And, unlike similar OS-specific features such as the MacOS ‘alias’ or the Windows ‘shortcut’, symlinks are almost universally understood by software - Sononym included. So the link itself don’t take up more than a few bytes of hard disk space. In practice, your operating system simply understands a symlink as a reference to a file. So you could create a file on your desktop that references a file somewhere else on your harddrive, and as a result, access the same file from two different places. Symlinks are a feature of your operating system that allows you to place “references” to files or folders situated in a different location on your computer. We will not take responsibility for any potential data loss that is caused, directly or indirectly, by the instructions provided in this article. ⚠️ IMPORTANT: As with any operation performed on your file system, it’s absolutely essential that you understand what you’re doing. Under some circumstances, this approach can speed up the initial access time dramatically.Īll you need is a hard drive or SDD with a few gigabytes of available space (for storing databases), and the skills to create symbolic links. This is achieved by moving libraries onto that media, and then using symlinks to “trick” the application into thinking that the files are also located there. The technique is based on a very simple idea: to bring Sononym databases close to the application / onto a faster media. Hiding sononym.db files (to keep those sample folders nice and tidy).Sharing a pool of samples with other people while working in a team setting.Ability to index folders which are otherwise marked as read-only.Ability to merge sample folders which are scattered across your computer.Speeding up access to (very) large sample collections, or files located on a network (NAS).But first, here’s a quick mention of some scenarios where symlinks can make a positive difference in Sononym: If not, don’t worry, we will briefly explain the concept. If you are an advanced user, you probably already have come across the term ‘symlink’, or ‘symlinking’. This article is going to demonstrate how symbolic links (symlinks) can make a difference in Sononym.
0 Comments
Leave a Reply. |