December 15, 201015 yr Hi guys, Let's say you have the following structure under a user share: /--- Movie 1 (on Disk 1) Movies---|---- Movie 2 (on Disk 2) \--- Movie 3 (on Disk 3) So what happens when I try to access /Movies/Movie 2, for example? Would it spin up all 3 disks to figure out which one contains Movie 2?
December 15, 201015 yr Hi guys, Let's say you have the following structure under a user share: /--- Movie 1 (on Disk 1) Movies---|---- Movie 2 (on Disk 2) \--- Movie 3 (on Disk 3) So what happens when I try to access /Movies/Movie 2, for example? Would it spin up all 3 disks to figure out which one contains Movie 2? Yes, "Movies" is the share and is visible on all three drives. unRAID only cares about that top level folder, so it will spin up all three drives to find out what is under "movies"
December 15, 201015 yr Hi guys, Let's say you have the following structure under a user share: /--- Movie 1 (on Disk 1) Movies---|---- Movie 2 (on Disk 2) \--- Movie 3 (on Disk 3) So what happens when I try to access /Movies/Movie 2, for example? Would it spin up all 3 disks to figure out which one contains Movie 2? Yes, "Movies" is the share and is visible on all three drives. unRAID only cares about that top level folder, so it will spin up all three drives to find out what is under "movies" It is possible for the directory entries to already be in the disk buffer cache if they were recently accessed. When that occurs there is no need to spin up the disks at all. A while ago I wrote a program that would reside on the unRAID server and every few seconds read the directories of the user shares to keep them from being dropped from the buffer cache. (The least-recently-used blocks are re-used when new files are accessed) That program is named cache_dirs It is described here in the wiki http://lime-technology.com/wiki/index.php?title=Improving_unRAID_Performance#Keep_directory_entries_cached
December 15, 201015 yr Hi guys, Let's say you have the following structure under a user share: /--- Movie 1 (on Disk 1) Movies---|---- Movie 2 (on Disk 2) \--- Movie 3 (on Disk 3) So what happens when I try to access /Movies/Movie 2, for example? Would it spin up all 3 disks to figure out which one contains Movie 2? Yes, "Movies" is the share and is visible on all three drives. unRAID only cares about that top level folder, so it will spin up all three drives to find out what is under "movies" It is possible for the directory entries to already be in the disk buffer cache if they were recently accessed. When that occurs there is no need to spin up the disks at all. A while ago I wrote a program that would reside on the unRAID server and every few seconds read the directories of the user shares to keep them from being dropped from the buffer cache. (The least-recently-used blocks are re-used when new files are accessed) That program is named cache_dirs It is described here in the wiki http://lime-technology.com/wiki/index.php?title=Improving_unRAID_Performance#Keep_directory_entries_cached Yup, I understand that but did not want to confuse, muddy the waters right off the bat. On stock unRAID it is unlikely that a spinup would not occur.
December 15, 201015 yr Author It is possible for the directory entries to already be in the disk buffer cache if they were recently accessed. When that occurs there is no need to spin up the disks at all. A while ago I wrote a program that would reside on the unRAID server and every few seconds read the directories of the user shares to keep them from being dropped from the buffer cache. (The least-recently-used blocks are re-used when new files are accessed) That program is named cache_dirs It is described here in the wiki http://lime-technology.com/wiki/index.php?title=Improving_unRAID_Performance#Keep_directory_entries_cached Cool stuff! I will try cache_dirs for sure. Thank you!
Archived
This topic is now archived and is closed to further replies.