W10 slowdown

[Nenad Batoćanin]

Windows 10 machine acting "server" with only one "client" (W10 too, but this is not important). HB application is on shared dir on the "server", "client" use the same folder. When program run only on one machine, everthing is fine. But, when program is started simultaneosly on both machines, program on "client" became incredibly slow. We change net adapter settings/drivers, disable Aero, adjust server for "best performance", setting "processor sheduling" to "Background services", disable AV program... without visible efects. 

Any suggestions? 

Regards, NB

[Klas Engwall]

Hi Nenad,

What about oplocks?

Regards,
Klas

[Nenad Batoćanin]

Hi Klas!

Sorry for the delay :(

Yes, oplocks is disabled on this machine. Turn on oplocks will probably speed up, but then I have a another problem?

Regards, NB

[Klas Engwall]

Hi Nenad,

> Yes, oplocks is disabled on this machine. Turn on oplocks will probably
> speed up, but then I have a another problem?

Didn't you get that backwards? If oplocks are on, the first user will
have a speed advantage but everyone else will have to pay for that. And
about "this machine", the registry settings have to be "hacked" on all
involved machines along the lines that have been discussed here many
times. Only the server or only the workstation is not enough.

Regards,
Klas

[Francesco Perillo]

Can it be that oplocks need to be disabled in some other ways?

Can you setup a linux server with a recent samba and run tests with oplocks enabled and disabled?

Linux smbstatus also shows which protocol is used for the connection.

Disabling oplocks on my samba server has serious speed impact on some of my full table scan reports.

--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-users+unsubscribe@googlegroups.com
Web: http://groups.google.com/group/harbour-users

---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nenad Batoćanin]

We did not set up the machine, it worked the other team. I think the oplocks is off on both machines, but I'm not sure (I will check). Currently the system is unusable, because users can work only on the server or on ws. When working user 1 (server), the user 2 can not work. 

But, I think I can enable oplocks in this case because user-1 99.9% of time only looking for data (reports, etc.) and user-2 writes data. 

Regards, NB

[Klas Engwall]

Hi Nenad,

> We did not set up the machine, it worked the other team. I think the
> oplocks is off on both machines, but I'm not sure (I will
> check). Currently the system is unusable, because users can work only on
> the server or on ws. When working user 1 (server), the user 2 can not work.

Yes, that is typically what happens when oplocks are on. User one opens
files and gets quick responses because the server puts opportunistic
locks on the files. When user two tries to open them (whether for
reading or writing) the server starts negotiations with user one's
computer for each involved file and asks user one to release the locks.
That takes time. Opening ten dbf files with ten ntx files each results
in 110 separate negotiations ...

> But, I think I can enable oplocks in this case because user-1 99.9% of
> time only looking for data (reports, etc.) and user-2 writes data.

It doesn't matter who is reading and who is writing. The entire file is
locked by user one (even if he is only reading) until the opportunistic
lock is lifted, and user two cannot open it at all while the negotiating
goes on. Locking a record for writing is an entirely different lock.

I think you would benefit from searching the web for in depth
descriptions of oplocks (especially by other providers of filesharing
database systems, like Dataflex for example) to read up on what actually
happens in the SMB protocol. And don't forget to also investigate all
the other settings that can be found in contrib\hbwin\win_os.prg
(cachedopenlimit, SMB2 etc, etc).

There are also many previous discussions in this group, so search for
those too.

Regards,
Klas