You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wondering if any light could be shed on why I'm seeing extremally slow performance using the smb_fs on a Windows 11 system.
I haven't done exhaustive profiling, but reading a small text file from an smb share on an ubuntu server on my local network takes around 3.6 seconds using smb_fs.readtext(), where reading the exact same file from the exact same smb server using a drive letter mount on my windows machine using OSFS.readtext() takes around .008 seconds.
I'm not sure how much caching the windows smb mount system is doing (that was my first thought), but a 450x difference is very noticeable (which is why I perfed it in the first place) and if this delay stays consistent across the board, makes this pretty unusable for my purposes (which is unfortunate because it would be really cool to enable access to these files without having to configure the network drive letter mapping first).
Is this something I'm potentially doing when constructing the object, or something inherent to the way SMB is being utilized? It doesn't seem to be an overhead in the fs library itself as the osfs object shows no such performance drop.
The text was updated successfully, but these errors were encountered:
Wondering if any light could be shed on why I'm seeing extremally slow performance using the smb_fs on a Windows 11 system.
I haven't done exhaustive profiling, but reading a small text file from an smb share on an ubuntu server on my local network takes around 3.6 seconds using smb_fs.readtext(), where reading the exact same file from the exact same smb server using a drive letter mount on my windows machine using OSFS.readtext() takes around .008 seconds.
I'm not sure how much caching the windows smb mount system is doing (that was my first thought), but a 450x difference is very noticeable (which is why I perfed it in the first place) and if this delay stays consistent across the board, makes this pretty unusable for my purposes (which is unfortunate because it would be really cool to enable access to these files without having to configure the network drive letter mapping first).
Is this something I'm potentially doing when constructing the object, or something inherent to the way SMB is being utilized? It doesn't seem to be an overhead in the fs library itself as the osfs object shows no such performance drop.
The text was updated successfully, but these errors were encountered: