photools.com Logo

IMatch and NAS Systems (Network-Attached Storage)

What’s a NAS?

A NAS unit is a computer connected to your network that only provides file-based data storage services to other computers on the network. There are cheap NAS systems and quite expensive ones. They differ in reliability and performance.

Can I keep my IMatch database and image files on the NAS?

Yes. And No. IMatch can work with databases and images stored on NAS systems in your network. The database and images can be shared (if multiple users work with IMatch, every user needs an IMatch license of course).

But, keeping the database on a NAS will result in a severe performance penalty. A NAS can be 1,000 times slower than a SSD installed in your computer. And this slows down everything IMatch does, from accessing files to searching the database. We highly recommend to always store the database on your fastet SSD for optimal performance.

Use UNC Shares

You can either use a drive mapping or (better) UNC paths like (\\server\share\folder) to address the files on your NAS system from within your IMatch database. UNC paths have the advantage to be unique within your network and accessible from all computers in your network without the need to create a drive mapping first.

Performance

The performance of such a configuration depends on your network speed and the performance of the NAS system. Usually the database performance suffers badly when the database file is stored on a NAS. That’s not the fault of IMatch, it’s just how it is.

What you have to keep in mind is that most NAS systems are designed for streaming usage. This means they are intended to keep your backups, and to deliver video, image and audio data. And they usually do a great job with this.

Keeping your images on the NAS box is usually no problem and performance will be OK. Indexing files stored on NAS is considerably slower than indexing images stored on a local SSD or spinning disk. But once the image has been indexed, operations like viewing or searching will be as fast as local images.

Keep Your Database on a SSD for Optimal Performance

But the IMatch database file is a different matter. When you work with IMatch, IMatch reads and writes very often from and to the database file. These are usually small changes of a few bytes to a few kilobytes. And, especially for cheaper NAS systems, this creates a worst-case scenario. Many small read/write operations over the network are bad for the performance and thus the overall IMatch performance will suffer. Even a moderately fast built-in hard disk is 50 to 100 times faster than NAS storage. And an SSD is 1,000 times faster.

How to Test

If you experience performance problems with IMatch in a NAS environment, just copy your database from the NAS system to your local hard disk. Then open the database from there via the Database menu > Open command in IMatch. If your NAS is the performance bottleneck you will notice a much snappier response time and overall better speed with a SSD or spinning disk in your PC.

Worst Worst-case Scenario

The worst worst-case scenario is keeping the IMatch  database on a NAS which is only connected by wireless (WLAN) to your computer. The latency of such connections may be OK for image storage, but not for your database.

Virus Checkers

Sometimes, virus checkers interfere and slow-down IMatch considerably. If your virus checker constantly scans the IMatch database on disk or intercepts every read/write access IMatch makes to files on your NAS, performance will suffer.

If you suspect that the virus checker interferes (or it even tells you so), make sure to add exceptions/exclusions for the folder containing your IMatch database. And (temporarily) make an exception/exclusion for the IMatch executable while you test NAS performance.

A Workflow Suggestion

If possible, finish your images while they are stored on your SSD. This means editing them and creating the final results and versions. Index them in IMatch, add metadata, and write back to store the metadata safely in the image (or XMP sidecar file). Once the images are final, move the folder to your NAS for long-term archiving.

This gives you the best possible performance while actively working with your images. Viewing them later, searching, and other operations you perform in IMatch are as fast for images stored on NAS as they are for images stored locally on your PC.

The IMatch cache is stored on your local SSD and previewing images is equally fast for local images and images stored on the NAS. When you notice delays while working with JPG images, it’s because IMatch by default does not cache JPG images and has to fetch them from the NAS when you want to view them.

If this becomes an issue, change the cache options in IMatch to also cache JPG files.

Conclusion

IMatch is, basically, a high-performance database system. Storing the IMatch database on your fastest SSD is mandatory for excellent performance.

IMatch works fine with images and other files stored on NAS, but performance will be slower compared to images stored on a spinning disk or SSD in your computer. Especially operations like indexing files or metadata write-back suffer from the much slower response times of a NAS.

You can overcome this by finishing the files while still on your SSD, and then move them to your NAS for long-term archival.