A late reply and thank you, Larry, for the site below. It's a great site.
Unfortunately, our testing shows that the setting on that particular page
makes no difference to the problem we are experiencing.

We have now tested the performance on three different W2000 servers, and
compared that to various W98 boxes and NT 4.0 servers.  In all cases, the
W2K server FLIES when only one workstation is connected to the database. We
tested using rbdos versions from 6.1A through 6.5+, and with rbWin 6.5+.

When a second workstation connects to the database, performance drops by a
huge factor - up to 10X the time.to perform a two table update. The second
workstation is idle, merely connected and sitting at the R> prompt.

We have tested on NT 4.0 servers and W98 servers and one W95 server, and the
problem does not occur on any of these.  The W95 server, live with 11 users,
outran the W2000 server in one environment by a factor of 2.5x.  The W95's
hardware is old - PII 233, 64 Mb RAM. The W2000 server is a brand new Dell
with plenty of horsepower.

FYI, and of no use to anyone, probably,  - I connected my notebook to the
database with two independent sessions, (R:Base local, and network) and the
degradation did not happen.  The server monitor showed a single connection,
even though R:Base correctly knew that two users were in the db.

We tested this, as a point of interest, and R:Base would not connect the
second session when the first session was SET MULTI OFF.

Howard Simon duplicated these results with his notebook, on a different
network node. Hmm, R:Base is smarter than Windows 2000, it would appear.


----- Original Message -----
From: "Lawrence Lustig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 11:24 AM
Subject: Re: Network Stations SLOW


> > The slowness is evident in both starting up the
> > application and then
>
> Here are a couple of ideas from a web search:
>
> Problem: Windows redirector does not use caching under
> certain circumstances:
> http://www.jsiinc.com/SUBE/tip2100/rh2145.htm


Reply via email to