Hi Chris,

> Thanks Christof, assuming at the moment this was the issue did you manage to 
> speed it up?  Was there a configuration on the client which determined how 
> many packets could be exchanged?

No, in this case it was handed over to the IT people. Setting up an extensive 
virtual network with various Windows servers was on my todo list for a long 
time, but I never found the time to actually install and configure all these 
machines.

There are just too many variables that could have an impact. Like there is SMB 
signing where packets are signed and validated. With signing the certificate 
infrastructure might have an impact. There are various ways to configure 
network throughput on the servers as well as on any router and switch in 
between. There's also a growing number of "smart" solutions that tries to 
optimize network throughput, but makes it really hard to get repeatable 
results. On top of that there might be extra services on the server from 
obvious ones like virus scanners, to less obvious ones such as filter drivers 
for distributed file systems. 

Then there's the whole thing of OpLocks and client side caching that impacts 
performance and stability depending on whether a file is used, has recently 
been used, or is not used by more than one client machine in the network.

Plus SMB 2.x/3.x is a protocol that dynamically adjusts its behavior based on 
network performance and quality. 

Whatever the reason is, the fewer read/write requests you make, the better your 
application will perform, if that is the cause of your problem, even when you 
can't fix the network.

Other reasons might include a larger number of users adding records, modifying 
memo fields or updating index fields. All of these are operations that require 
exclusive access in FoxPro and therefore can only be performed by one client at 
a time. These operations lock the table, index and memo field header, 
respectively. That would be an entirely different problem that in ProcMon you 
would notice with locker than usual times between the LockFile and the 
Read/WriteFile lines as well as the total number of LockFile requests for each 
period of using the application when monitored on the server.

-- 
Christof
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/3c13c343-c104-4893-b16b-dd25a7d91...@wollenhaupt.org
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to