Hello

I encounter this problem in the past but can't figure if there is a
solution.

When several users work on the same app on a network enviroment
the first user can work fast (2-3 sec. to open a query)
the second user work very slow (30 sec. to open the same query) .

I'm using ver 2.04b2

Thanks
Sorin

Sorin

I'm guessing fileserver. If so I think this is a problem that's been encountered many times and is to do with the way Windows applies file locks. There's nothing Tim can do about it.

Roy Lambert [Team Elevate]

Thanks

The app and the database are on a server and the user work from station
networked to this serever.
Do you call it file server?

Thanks
Sorin

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
>
> I'm guessing fileserver. If so I think this is a problem that's been
> encountered many times and is to do with the way Windows applies file
> locks. There's nothing Tim can do about it.

Sorin


It sort of sounds like it. The simple way to figure it out is that if its not client/server then its fileserver.

Roy Lambert [Team Elevate]

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
>
> It sort of sounds like it. The simple way to figure it out is that if its
> not client/server then its fileserver.

No, it's not client/server
Quite a problem. Those are clients that I migrate from bde and now they
request to go back.

Thanks
Sorin

Sorin

If the environment is file server instead of client server, then I am pretty
sure the problem is related with opportunistic locking settings on Windows
server.

Check windows registry

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
OplocksDisabled should be 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks should be 0

BTW, my suggestion is to change to client/server.
The application will run better (in general) than file server. It is more
secure too.

Eduardo

"Eduardo [HPro]" <contato@hpro.com.br> wrote in message
> If the environment is file server instead of client server, then I am
> pretty sure the problem is related with opportunistic locking settings on
> Windows server.
>
> Check windows registry
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
> OplocksDisabled should be 1
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
> EnableOplocks should be 0
>
> BTW, my suggestion is to change to client/server.
> The application will run better (in general) than file server. It is more
> secure too.

Thanks

Can I change those parameters on my clients registry machine without fear to
cause others problem?

I'll be happy to shift to client/server but this, I think, will demand lots
of changes on my app
so I postpone it meanwhile.

Thanks
Sorin

Sorin,

<< I encounter this problem in the past but can't figure if there is a
solution.

When several users work on the same app on a network enviroment the first
user can work fast (2-3 sec. to open a query) the second user work very slow
(30 sec. to open the same query) . >>

Try increasing the buffer sizes for your tables (several MB may help).
Apart from that, this is just due to the way that opportunistic locking
works in the SMB (and SMB2) protocols that are used by Windows for
file-sharing.  You can try disabling it, like Eduardo recommends, but that
should only result in the first user's open getting slower.  However, if it
does improve the performance of the second open, please post the results
here.  The "breaking" of the op-locks is not supposed to take very long, but
it may take a while in certain cases, and it would be interesting to know if
you're seeing one of those cases.  "Breaking" basically involves the file
server telling the first client to stop buffering data locally because
another client has connected.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
>
> Try increasing the buffer sizes for your tables (several MB may help).
> Apart from that, this is just due to the way that opportunistic locking
> works in the SMB (and SMB2) protocols that are used by Windows for
> file-sharing.  You can try disabling it, like Eduardo recommends, but that
> should only result in the first user's open getting slower.  However, if
> it does improve the performance of the second open, please post the
> results here.  The "breaking" of the op-locks is not supposed to take very
> long, but it may take a while in certain cases, and it would be
> interesting to know if you're seeing one of those cases.  "Breaking"
> basically involves the file server telling the first client to stop
> buffering data locally because another client has connected.

Thanks

The query is selected from several tables. To increase the buffer of all?

Any specific buffer to increase page size, max row, etc.. or to increase
all?

Increasing will not have impact on others enviroment? The same app work also
as standalone and terminal/server.

Thanks
Sorin

Sorin,

> I'll be happy to shift to client/server but this, I think, will demand lots
> of changes on my app
> so I postpone it meanwhile.

Don't worry: there are only small changes in the application, but the
benefits are great.

Just setting some properties are enough:

Sample:

procedure Tdm.MySessionBeforeConnect(Sender: TObject);
var
  CurrentIP: string;
begin
  CurrentIP := RegReadCommonString('RemoteAddress');
  if CurrentIP = '' then
  begin
    // Display a setup-form that requests the correct IP of EDBServer
  end;
  MySession.SessionType := stRemote;
  MySession.RemoteAddress := CurrentIP;
end;

You can also use the "RemoteHost" property instead of the
"RemoteAddress" property. In that case you have to assign the name of
the remote machine.

Regards Uli