Re: ( opportunistic ) locking, LAN problems

Tim,

What's worked for me, though possibly very different environment, is this
Registry tweak file. Paste this in a Notepad file, and name it anything, with
the extension ".reg" When you activate it, the settings will be made
in the Registry automatically. NOTE: this is a very dangerous tool in the wrong
hands.

**********************
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Paramete
rs] "UseOpportunisticLocking"=REG_DWORD:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"EnableOplocks"=REG_DWORD:00000000
**********************

However, it may not be Windows that is the problem. If you have a very complex
form with lots of pages of detailblocks, it may put a burden on both resources
and net traffic I think. This might have to do with the way forms force
Superbase to read the files, but I'm hazy about that. The idea is that reading a
detailblock can require Superbase to make several passes through a file,
depending on how the detailblock is linked, etc.

I've heard that people get good results using Terminal Server, could this be
worth trying? It might put the heaving lifting back on the server, instead of
across the net? Just a guess...

Peter



On Tue, 12 Dec 2006 07:30:14 -0500, Tim <sbug@dr-byte.com> wrote:

> Hi everybody,
> using SB2001 (544) in a LAN (SBS2003 server, W2k- and WXP-Clients) we
> expirience following behavior:
> The app consist of roughly 50 files (with 1-500.000 records), all files
are
> opened at start of app share,0. Once the app is started from one client,
> loading of files is fast. Opening a 7-pages SBV with lots of detailblocks
> and related files is fast, too. Starting the app a second time on the same
> client gets same result: loading files = fast / opening SBV = fast. If the
> app is started on another client loading of files remains fast, but
opening
> the SBV takes not 1-2 seconds, it takes 20-30 seconds!! If client no.1 (or
> no.2) ends the app, opening the SBV still takes 20-30 secs for the
remaining
> client. Loading/opening on the server (since local) stays fast, no matter
> if/how many clients start app.
>
> We tried everything concerning deleting sb! and superbas.net (only 1),
> sblocal=none, OpLocks and all things listed on superbase.com, using
> Windows-Domains or Workgroups, all kinds of Windows-systems = problem
stays.
> We saw, that locking/unlocking takes places hundreds of times on the
> server-machine (superbas.net, sb!)
>
> What are the correct settings concerning OpLocks? Are there any other
tricky
> things involved?
> THX in advance
> Tim
>
>
>

Hi everybody,
using SB2001 (544) in a LAN (SBS2003 server, W2k- and WXP-Clients) we
expirience following behavior:
The app consist of roughly 50 files (with 1-500.000 records), all files are
opened at start of app share,0. Once the app is started from one client,
loading of files is fast. Opening a 7-pages SBV with lots of detailblocks
and related files is fast, too. Starting the app a second time on the same
client gets same result: loading files = fast / opening SBV = fast. If the
app is started on another client loading of files remains fast, but opening
the SBV takes not 1-2 seconds, it takes 20-30 seconds!! If client no.1 (or
no.2) ends the app, opening the SBV still takes 20-30 secs for the remaining
client. Loading/opening on the server (since local) stays fast, no matter
if/how many clients start app.

We tried everything concerning deleting sb! and superbas.net (only 1),
sblocal=none, OpLocks and all things listed on superbase.com, using
Windows-Domains or Workgroups, all kinds of Windows-systems = problem stays.
We saw, that locking/unlocking takes places hundreds of times on the
server-machine (superbas.net, sb!)

What are the correct settings concerning OpLocks? Are there any other tricky
things involved?
THX in advance
Tim

Hi Peter,
thanks a lot for your answer.
- we made exactly these settings in the registry (manually) of the server
and recommended ones on the clients.
- it is a complex form with lots of pages of detailblocks. BUT: open it on
one(!) client and it's there in a second. Even starting the app on this
client machine a second, third or fourth time still opens the form very
fast. So heavy net traffic can't be the answer ?!?
- it must have to do with windows' locking. It slows down to 20-30 seconds,
once another client on the LAN opens the form.

Maybe somebody's got the answer - before we try using a Terminal Server ;-))
Thanks
Tim

-----------------------------------------
"Peter Barus" <peter@visualpricing.com> schrieb im Newsbeitrag
news:op.tkgbdtempcvzm2@fudoshin...
Tim,

What's worked for me, though possibly very different environment, is this
Registry tweak file. Paste this in a Notepad file, and name it anything,
with the extension ".reg" When you activate it, the settings will be
made in
the Registry automatically. NOTE: this is a very dangerous tool in the wrong
hands.

**********************
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Para
meters] "UseOpportunisticLocking"=REG_DWORD:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameter
s] "EnableOplocks"=REG_DWORD:00000000
**********************

However, it may not be Windows that is the problem. If you have a very
complex form with lots of pages of detailblocks, it may put a burden on both
resources and net traffic I think. This might have to do with the way forms
force Superbase to read the files, but I'm hazy about that. The idea is that
reading a detailblock can require Superbase to make several passes through a
file, depending on how the detailblock is linked, etc.

I've heard that people get good results using Terminal Server, could this be
worth trying? It might put the heaving lifting back on the server, instead
of across the net? Just a guess...

Peter



On Tue, 12 Dec 2006 07:30:14 -0500, Tim <sbug@dr-byte.com> wrote:

> Hi everybody,
> using SB2001 (544) in a LAN (SBS2003 server, W2k- and WXP-Clients) we
> expirience following behavior:
> The app consist of roughly 50 files (with 1-500.000 records), all files
are
> opened at start of app share,0. Once the app is started from one client,
> loading of files is fast. Opening a 7-pages SBV with lots of detailblocks
> and related files is fast, too. Starting the app a second time on the same
> client gets same result: loading files = fast / opening SBV = fast. If the
> app is started on another client loading of files remains fast, but
opening
> the SBV takes not 1-2 seconds, it takes 20-30 seconds!! If client no.1 (or
> no.2) ends the app, opening the SBV still takes 20-30 secs for the
remaining
> client. Loading/opening on the server (since local) stays fast, no matter
> if/how many clients start app.
>
> We tried everything concerning deleting sb! and superbas.net (only 1),
> sblocal=none, OpLocks and all things listed on superbase.com, using
> Windows-Domains or Workgroups, all kinds of Windows-systems = problem
stays.
> We saw, that locking/unlocking takes places hundreds of times on the
> server-machine (superbas.net, sb!)
>
> What are the correct settings concerning OpLocks? Are there any other
tricky
> things involved?
> THX in advance
> Tim
>
>
>

On Wed, 13 Dec 2006 07:01:45 -0500, Tim <sbug@dr-byte.com> wrote:

> once another client on the LAN opens the form.
>


That is net traffic, is it not? Perhaps Neil or somebody with more knowledge can
say for certain, but I believe the form can require a lot of back-and-forth
while Superbase re-reads the file several times if it is very complex. Across a
network this could be slower.

Tim wrote:
> Hi Peter,
> thanks a lot for your answer.
> - we made exactly these settings in the registry (manually) of the server
> and recommended ones on the clients.
> - it is a complex form with lots of pages of detailblocks. BUT: open it on
> one(!) client and it's there in a second. Even starting the app on this
> client machine a second, third or fourth time still opens the form very
> fast. So heavy net traffic can't be the answer ?!?
> - it must have to do with windows' locking. It slows down to 20-30
seconds,
> once another client on the LAN opens the form.
> 
> Maybe somebody's got the answer - before we try using a Terminal Server
;-))
> Thanks

I have seen this sort of behavior before, but only in a mixed netwrok
environment between a server as of Windows 2000 SP5 or later (XP, etc.)
and clients that were on Windows 2000 SP4 or ealrier (including NT 4,
98, Me). The problem is that the two are using virtually incompatible
versions of the TCP/IP protocol. There was a major change in the TCP/IP
implementation at that point and this was a common problem. I am unclear
if this environment maps to yours however.