- Slow samba music update#
- Slow samba music Pc#
- Slow samba music windows#
Even when just loading the tagdata (not the audio/file itself)
Old, single harddisk under Windows: 50 files/sec. Diskpool (SMB Share tuned) on FreeNAS: 25 files/sec. Folder loading: (open a folder in MP3Tag wait for all file-data/tag-data to be listed). So the more files per MB, the slower it goes. Batch with 40MB-files ~30% faster than 10MB-file-batch. So: diskpool and network are OK yet actual speed drops >50% due to Samba-handling?. Actual transfer-speed: ~350 MB/s (copy-paste RAMdisk on W10-PC Samba-share). Workload consisting of large files/large blocks less files/MB, less records/MB. Otherwise all FreeNAS –users using Samba would have a very very slow system. Normal thinking leads to the conclusion that something must be wrong in my settings. So if I am already having such slow performances (for file-transfers, for folder loading etc), how bad will the performance be for workloads with normal (avg 1MB) files…? And normal 128kB-records.? In contrary: the workload makes it much easier on the system. 
So in conclusion there is no ‘special circumstances’ here that makes it heavier on the system.
Slow samba music Pc#
Also then the continuous waiting before the PC is ready and you can continue your work is not normal.
Yet this does not matter for the performance: also transferring just 5.000 files gives the same slow speed/second. transferruns are fairly high (typically 100-200.000 files). The number of files in the storage is fairly high (~1-2 million). So this is not ‘metadata-heavy’ workload in contrary: it’s 25 x 8 = 200x less heavy from normal load. This too makes it much easier on the system to handle these files. Having a 1MB (1024kB) recordsize in stead of the standard 128kB recordsize, means having 8x less records ergo 8x less metadata that needs to be registered. I am currently using recordsize of 1MB (have also experimented with 4MB but this did not give better performances). Moreover: because the files-size is that large (10MB minimum), I can use very large recordsize/blocksize. In general it will be 50.000 files (avg 1MB file). In my case this is about 2.000 files (avg 25MB file). A use-case having large files makes it easier on the system to handle say 50GB of data. So: this is NOT a case of small files on contrary: it’s a case of fairly large files (only large video’s or movies have larger files). My collection as indicated consists of only music-files in either ~10.000kB (10MB) size or ~40.000kB (40MB) size. Emphasis in NAS-storage is on the above orange area. File-sizes in general data-collections are:. Re ‘lots of small files’ ergo special circumstances Solving best by first identifying where the problem is. So not a 'heavy case' but instead an 'easy case' for the system. 
It's NOT 'small' files but instead large files. (this perhaps especially being noticed by 10Gb-users and/or people have gotten used to the slow system). So either something is wrong/missing in my settings or Samba all the time is bugging down the performance of FreeNAS. Also I do not believe that there is ‘special circumstances’ in this use-case or set-up.And then to act on that in a focused way. But also I believe it is more functional to determine first what the problems are that cause the poor performance.
Slow samba music update#
So I will update to the Beta –version and see what happens. I am prepared to try and experiment lots.And that latest Beta-version might help (and Beta-version to come might even better). Main points raised are that poor performance is due too special circumstances. Dataset: sync off, compress on, 1MB record/blocksize case Insensitive Windows-share
Slow samba music windows#
Interface: added the 'MTU 9000 up' (to use the large segment size) and also the '4096 rx' and '16384 tx' (to use the larger windows sizes)(I think this is) (on the rx I get a 'wrong value' comment in the boot-log) Large file-transfers/listings/deletes or tagdata-writes, by hand or by means of processing software. data-load: mass quantities (~2 million) of audiofiles 10MB/40MB (50/50) critical processes are only between Workstation and FreeNAS (10Gb peer to peer). Windows PC: running on Windows10 (dual Xeons E5-2660 / 32 GB RAM / mobo-based 10Gb NIC (FSP+) set-up of the FreeNAS-unit: see signature Did not help.ĭoes anyone have a fairly good understanding or good experiences on how we can improve this performance?Īny input would be greatly appreciated as frankly at this moment the FreeNAS-unit is not usable. Is it not a pity that the good performance of FreeNAS is spoiled so badly? My impression is that this is due to Samba and how this handles the files?
0 kommentar(er)
