Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 10 of 15 total |
Shared files and S.O. performance |
Thu, Mar 29 2007 4:10 AM | Permanent Link |
This is a very strange and tested issue here.
Have a Win2003 server, not domain, sharing DBISAM files. W2k and XP clients. All machines are pretty new and fast, assembled today and a year the oldest. Application, built in Delphi 6 opens +/- 120 dbisam tables, shared in server. LAN is Gigabit. Open application for the FIRST client. While W2k machines opens all tables in less than 10 seconds, all XP machines spend 30-50 seconds for the same. If some client has opened yet application, then XP machines spend <10 seconds. Changing NICs, LAN switch from several vendors has no effect. Of course, having an stub application in server or client with tables opened all the time seems a solution, but an stupid one. (not secure backups, nor table altering ...) It seems opt-look issues or WXP registry configuration, but I can't found nothing similar anywhere. Any comment? Thanks in advance. Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. | |
Thu, Mar 29 2007 6:09 AM | Permanent Link |
"Jose Eduardo Helminsky" | Tiago
Try changing the following settings at Win2003 registry. I have changed this and the performance to open the tables had improved a lot. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters autodisconnect REG_DWORD 0xffffff enableforcedlogoff REG_DWORD 0x1 enablesecuritysignature REG_DWORD 0 EnableOplocks REG_DWORD 0 CachedOpenLimit REG_DWORD 0 Eduardo |
Thu, Mar 29 2007 6:39 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Tiago,
<< Have a Win2003 server, not domain, sharing DBISAM files. W2k and XP clients. All machines are pretty new and fast, assembled today and a year the oldest. Application, built in Delphi 6 opens +/- 120 dbisam tables, shared in server. LAN is Gigabit. Open application for the FIRST client. While W2k machines opens all tables in less than 10 seconds, all XP machines spend 30-50 seconds for the same. If some client has opened yet application, then XP machines spend <10 seconds. >> What happens if you remove the W2k machines and only have XP machines (and the 2003 server) on the network ? -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Mar 29 2007 7:07 AM | Permanent Link |
Tim,
>What happens if you remove the W2k machines and only have XP machines (and >the 2003 server) on the network ? Nothing, its always slow. More again. This morning, in a test environment: W2003 server with just only client XP new, from scratch machine. Slow. Same server, same client machine, with changed O.S. to w2k. Fast. Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. | |
Thu, Mar 29 2007 7:16 AM | Permanent Link |
Tim,
>What happens if you remove the W2k machines and only have XP machines (and >the 2003 server) on the network ? More on that. WinXP SP1 runs very fast. WinXP SP2 is slow. We are near the problem! Any suggestion? Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. | |
Thu, Mar 29 2007 11:41 AM | Permanent Link |
Michael Baytalsky | Firewall, antivirus, security features of SP2? Michael (Tiago Ameller) wrote: > Tim, > >> What happens if you remove the W2k machines and only have XP machines (and >> the 2003 server) on the network ? > > More on that. WinXP SP1 runs very fast. WinXP SP2 is slow. > > We are near the problem! Any suggestion? > > > Tiago Ameller > tiago put_an-a-_in_a_circle sistemasc.net > Sistema, S.C. |
Thu, Mar 29 2007 12:28 PM | Permanent Link |
Michael
>Firewall, antivirus, security features of SP2? None of them. All re-visited (!?) Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. | |
Thu, Mar 29 2007 3:04 PM | Permanent Link |
Dave Harrison | (Tiago Ameller) wrote:
> Tim, > > >>What happens if you remove the W2k machines and only have XP machines (and >>the 2003 server) on the network ? > > > More on that. WinXP SP1 runs very fast. WinXP SP2 is slow. > > We are near the problem! Any suggestion? > > > Tiago Ameller > tiago put_an-a-_in_a_circle sistemasc.net > Sistema, S.C. Have you tried removing IPV6 from the protocol list of your network cards? Also do you have MS's "Write Cache Enabled"? Try turning it off. Of course turn of MS's indexer if you have it running. Dave |
Fri, Mar 30 2007 10:38 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Tiago,
<< More on that. WinXP SP1 runs very fast. WinXP SP2 is slow. >> I'd start with that in terms of some Google searches. That usually reveals at least something interesting. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Mar 30 2007 11:10 AM | Permanent Link |
Eduardo
>Try changing the following settings at Win2003 registry. I have changed this >and the performance to open the tables had improved a lot. > >HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters > >autodisconnect REG_DWORD 0xffffff >enableforcedlogoff REG_DWORD 0x1 >enablesecuritysignature REG_DWORD 0 >EnableOplocks REG_DWORD 0 >CachedOpenLimit REG_DWORD 0 This classic topic does not help in this case. I've set this settings, and WXP clients are running the same bad way. W2k machines run a bit faster. Thanks. Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |