Samba performance degraded with simultaneous NFS access

[Lapin]

Hi folks,

I'm using a WD HD TV Live with B-Rad wdlxtv firmware.
I enabled the direct NFS mount sharing in order to be able to directly access my DS207+ without using DLNA.
Everything is working fine, excepted that when a HD movie is streamed on the WD through NFS, then the samba access performance is very degraded.
Typically, the read with samba will not exceed 1or 2Mo/s (same for write) if the streaming is going on NFS (HD movie requires about a 1.5Mo/s constant read).
The home network is wired with Cat6 cable, and all my switches are professional Netgear ones.
The limitation is definitely coming from the NAS.
If I exclusively use samba access, then I'm able to reach the DS207+ limits (R|W: 20|16Mo/s).

Did somebody observe the same issue?
Any help or tip will be very welcome.

[Lapin]

As always, the Synolgy's support is great. So, I got a hotfix from Synology.

I installed the hotfix. This didn't change the firmware version (still 3.0-1337), however my DS207+ did reboot. The log entry confirmed that the update was successful.
I've done two tests:
1- streaming a huge m2ts 1080p video through NFS to my WDHDTV and copy a file through samba from my laptop to my DS207+. NAS write speed was OK (9.8Mo/s from my 100Mbps laptop's network).
2- streaming a huge m2ts 1080p video through NFS to my WDHDTV and copy a file through samba from my DS207+ to my laptop. NAS read speed was NOT OK. It is desperately stuck at 512ko/s to 1Mo/s.

In both cases CPU usage is less than 20%.

In conclusion the hotfix just partially fix the problem. NFS read + samba write is OK, but NFS read + samba read is KO.
Last point, the constant rate during NFS read streaming is about 1.5Mo/s.

Maybe the next path will solve my problem?

If the big mkv video is streamed through DLNA, I don't have those issues. So, there is definitely something wrong with simultaneous NFS/Samba access.

[gangsterwagen]

Look at this, waiting for fix.

viewtopic.php?f=162&t=28846

[Lapin]

Thanks gangsterwagen!!


I thought I was the only one getting this issue.
Look like we need to wait for a patch...