On Sat, Mar 27, 2021 at 09:58:47AM +0100, Stefan G. Weichinger via samba wrote:> >Situation: > >Debian 10 domain member server with Version 4.13.5-Debian > >The hardware is some years old, 4 SAS disks (HUC101830CSS204) in hw >RAID6, RAID intact. > >2 gigabit NICs bonded on a uptodate switch. So ... not too bad. > >There are a few shares, one of them with a software that users start >from the network share (older accounting software). They start the >software from share1 and work with data on share2. > >The customer tells me that there are specific tasks in the software >that take a few minutes when run in that setup. > >The same task with the same customer data is much much faster when run >locally on the customer's PC. > >OK, expected. A modern SSD, locally ... etc etc > >But I don't think it should be minutes versus seconds, right?Need more details I'm afraid. "specific tasks...that take a few minutes" isn't enough to go on, sorry.
Am 29.03.21 um 19:38 schrieb Jeremy Allison:>> But I don't think it should be minutes versus seconds, right? > > Need more details I'm afraid. "specific tasks...that take a few minutes" > isn't enough to go on, sorry.Yes, I understand! I also don't know much about what they do. Basically they have several filebased databases opened, files like BL6F.DAT BL6F.IX (index, I assume) and some .DIA files That's small files, one whole subdir is maybe 20M per customer. And the tasks are some processing in their software, which will result in much read/write in all the above files. My assumption is that the locking behavior might influence the overall time needed here. That's why I excluded the DAT files via "veto oplock files", but that was years ago. What's the general recommendation here, especially with Windows10 clients?
Am 30.03.21 um 10:04 schrieb Stefan G. Weichinger via samba:> > Am 29.03.21 um 19:38 schrieb Jeremy Allison: > >>> But I don't think it should be minutes versus seconds, right? >> >> Need more details I'm afraid. "specific tasks...that take a few minutes" >> isn't enough to go on, sorry. > > Yes, I understand! > > I also don't know much about what they do. Basically they have several > filebased databases opened, files like > > BL6F.DAT > BL6F.IX (index, I assume) > > and some .DIA files > > That's small files, one whole subdir is maybe 20M per customer. > > And the tasks are some processing in their software, which will result > in much read/write in all the above files. > > My assumption is that the locking behavior might influence the overall > time needed here. That's why I excluded the DAT files via "veto oplock > files", but that was years ago. > > What's the general recommendation here, especially with Windows10 clients?Update: removing that "veto oplock files" statement improved the overall behavior. Customer is happy again.