![]() This defaulted to 32 (the maximum) but as a test, I downgraded it to just 3. You can see the version control is enabled. ![]() Let’s take a look at the version control settings: So we need to consider there is more than one thing contributing to the high disk IO. But the indexing seems to go on forever (at least, a long time). If indexing was the only issue, we would expect that, if the contents of the disk have been successfully index, then only minor indexing would be needed moving forward. Like I said in the intro to this article, the disks aren’t particularly good which would absolutely be contributing to this high utilization phenomenon. It’s showing the “disk” and “volume” utilization is extremely high. But why is it running? As the name would suggest, it’s indexing our files to improve search speeds and generally make findings files (by anything or anyone searching for them) faster – more efficient. You can see the resource hog is the “Universal Search” process and the “fileindexd” child process. Coupling that with the Synology insistence on high disk IO for (what would seem like) normal NAS-type work makes for a bad combination. The disks are 3.5 inch mechanical disks that honestly aren’t that great to begin with. In this example, we’re using the Synology DS720plus model. This article explains the primary reason for high disk utilization on the Synology NAS.
0 Comments
Leave a Reply. |