I just set all three registry settings back to their defaults:DirectoryCacheLifetime=10FileInfoCacheLifetime=10FileNotFoundCacheLifetime=5 There was no increase in speed. Anyone have any other advice? Thanks,Philip ---------- Original Message ---------- From: "Philip Borkholder" plborker@netzero.net To: profoxtech@leafe.com Subject: Re: DBFs Server 2012 R2 very slow with Certain Processors Date: Thu, 2 Jul 2020 17:24:16 GMT
Followup question Alan,When you stopped setting these to zero because Win 10 was "fixed" How did you leave the File Server LanManServer settings for :SMB1SMB2SMB3 Some recommendations out there state we need to shut off SMB2 & 3 and turn on SMB1 on newer File Servers This File Server has not shut off SMB2 or 3 My understanding was that the 3 Registry settings I listed were set to zero then to compensate for not shutting of SMB2 & 3 Thanks,Philip
---------- Original Message ---------- From: "Alan Bourke" alanpbourke@fastmail.fm To: profoxtech@leafe.com Subject: Re: DBFs Server 2012 R2 very slow with Certain Processors Date: Thu, 02 Jul 2020 17:44:36 +0100
On Thu, 2 Jul 2020, at 4:11 PM, Philip Borkholder wrote:
I set the LanManWorkstation settings for to avoid CDX corruption:[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters] FileInfoCacheLifetime = 0FileNotFoundCacheLifetime=0DirectoryCacheLifetime=0
Set them back to the defaults again (10 or 15 in each case IIRC), set to zero they can cause serious speed issues and aren't needed unless you are experiencing the particular corruption issues that zeroing them fixes. AFAIK recent Windows 10 versions have fixed whatever MS broke in SMB that caused these corruption issues in VFP (and MS Access).
Phil:
1. Can you confirm the local machine's network is actually running at full speed? Just because the driver thinks it's connected at 1Gbps doesn't mean it isn't rejecting 90% of packets. Try https://speedtest.net on this and another machine on the network to ensure there's not some blockage at the networking level.
2. Is it possible to (temporarily) move a set of DBFs locally to the machine, and see if the app runs okay with local data? This will determine if it is the local machine (bad CPU, bad RAM, something-something-local) or if the problem is the network or the server. In my experience, there's often a configuration problem on a new machine that needs adjustment. The machine's logs would show this.
3. Ensure the new machine is up to date in Windows updates and also drivers supplied by the vendor -- an amazing number of machines ship with software that doesn't work until it's updated.
On Thu, Jul 2, 2020 at 2:08 PM Philip Borkholder plborker@netzero.net wrote:
I just set all three registry settings back to their defaults:DirectoryCacheLifetime=10FileInfoCacheLifetime=10FileNotFoundCacheLifetime=5 There was no increase in speed. Anyone have any other advice? Thanks,Philip ---------- Original Message ---------- From: "Philip Borkholder" plborker@netzero.net To: profoxtech@leafe.com Subject: Re: DBFs Server 2012 R2 very slow with Certain Processors Date: Thu, 2 Jul 2020 17:24:16 GMT
Followup question Alan,When you stopped setting these to zero because Win 10 was "fixed" How did you leave the File Server LanManServer settings for :SMB1SMB2SMB3 Some recommendations out there state we need to shut off SMB2 & 3 and turn on SMB1 on newer File Servers This File Server has not shut off SMB2 or 3 My understanding was that the 3 Registry settings I listed were set to zero then to compensate for not shutting of SMB2 & 3 Thanks,Philip
---------- Original Message ---------- From: "Alan Bourke" alanpbourke@fastmail.fm To: profoxtech@leafe.com Subject: Re: DBFs Server 2012 R2 very slow with Certain Processors Date: Thu, 02 Jul 2020 17:44:36 +0100
On Thu, 2 Jul 2020, at 4:11 PM, Philip Borkholder wrote:
I set the LanManWorkstation settings for to avoid CDX
corruption:[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters]
FileInfoCacheLifetime = 0FileNotFoundCacheLifetime=0DirectoryCacheLifetime=0
Set them back to the defaults again (10 or 15 in each case IIRC), set to zero they can cause serious speed issues and aren't needed unless you are experiencing the particular corruption issues that zeroing them fixes. AFAIK recent Windows 10 versions have fixed whatever MS broke in SMB that caused these corruption issues in VFP (and MS Access).
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
-
Philip Borkholder -
Ted Roche