Tony wrote:
Just a few additional words to attempt and further clarify what was said above in cases where remote storage is involved:
If one has a NASLite-2 server set as a master to re-export the shares of a second NASLite-2 server (See the manual), the “Shares” share will include a folder called “Remote”. Moving files within the “Shares” share from/to “Remote” folders will result in traffic between the two NASLite-2 servers rather than traffic from NASLite-2 to client to NASLite-2.
Again, attempting to distill this so it’s clear, moving or copying files within a share will result in no traffic through the client. For example, if one maps the “Shares” folder as disk “S”, moving and copying files within disk “S” will result in no traffic through the client.
Hope that makes sense
Two questions:
1. What is the performance penalty to be expected when moving 700,000 small files in this fashion? Tests here suggest it is substantial. The first group of large files was moved very quickly, but a second batch of smaller files seems to be bogged down.
2. Would a superior implementation of iScsi improve such performance?
Login
Register
FAQ
Search
