I've been running a number of both RBD and RBW applications that connect to
the same database on a W2K server with a mixture of W2K Pro, NT
Workstation, and WIN98 clients. Total maximum number of simultaneous users
of the database is approximately 70. About 6 users access one of the
applications on the W2K server via Terminal Server. In addition, about 6
users access the database via Oterro and Crystal Reports on the W2K server
via Terminal Server and about another 20 access the database via Oterro and
Crystal Reports from their computers (again the same mixture as mentioned
above.) Some users also use Oterro and Excell to access the same database.
When I began to implement RTW (Runtime for Windows 6.5++) applications in
this environment I did not experience the type of throughput degradation
issues you mention in the original message below.
In some cases the RTW applications actually performed better than the RTD
applications, but in some others the RTD applications performed a bit
better.
Some considerations -
1) Make sure your Buffers and Files settings are at 60 for every user's
computer. I know that these settings are supposed to only affect DOS
programs, but I've found RBW and RTW to be very unstable without having
these settings in effect at the user's computer.
2) Make sure your W2K server has enough memory and a fast processor. The
minimum I use for file servers is 1GB of RAM and dual 933MHz PIII
processors.
3) Make sure your Win98 user systems have enough memory and fast
processors. You should have at least 128MB of RAM and a 400MHz PIII
processor on each user computer. Windows programs like RBW and RTW use much
more memory than DOS programs like RBD and RTD and if there is not enough
memory on the system the Windows programs will often load into virtual
memory (the user's hard drive). This can slow your Windows applications
down to a crawl. If you are providing specifications for new computers,
make sure they have at least 256MB of RAM and a 1.7MHz P4 processor. My
rule of thumb for deciding which processor to buy is to step down two or
three speeds from the fastest speed currently available. Today, 2.2MHZ is
the fastest speed available, however, 1.7MHz processors are still available
on the market and are much less costly than the 2.2MHz processors but are
quite fast.
Good luck!
Tony
Anthony Schmidt
President
The Computery Ltd.
One East Main Street
Bay Shore, NY 11706
Voice 631-665-8100
Fax 631-969-5988
|---------+---------------------------->
| | owner-rbase-l@son|
| | etmail.com |
| | |
| | 02/03/2002 01:38 |
| | PM |
| | Please respond to|
| | rbase-l |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc: (bcc: Anthony Schmidt/BayShore/SGU_LN)
|
| Subject: Re: Can we revisit W2K slowness?
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
Well, before they point their fingers at you,
Is their network hardware current?
Check for Throughput on each Segment?(to verify the cable isn't compromised
because it's unshielded and too close to fluorescent ballasts or there is
other complications?
10/100 cards in all machines?
10/100 Switch instead of hub?
Only running One Network Protocol? (If it's TCP/IP, how are the host names
being resolved? WINS? DNS? Netbios over TCP/IP still needs name resolution
for the fastest possible communication, otherwise it's on a seek mission
until the destination is resolved)
I have seen this small financial investment result in surprising changes
in
speed in "Small" networks where traffic volume didn't "Seem" to be an
issue.
----- Original Message -----
From: "tellef" <[EMAIL PROTECTED]>
To: "All" <[EMAIL PROTECTED]>
Sent: Sunday, February 03, 2002 12:09 PM
Subject: Can we revisit W2K slowness?
>
> I KNOW we have rehashed this a dozen times but how about
> one more time?
>
> I'm about to go live on a DOS-to-Windows conversion (up to date
> version of RBWin) on a W2K network with Win98 workstations. Their
> current 6.5+ DOS just flies and has never had any problems under
> this network. The speed is great and I've never had memory leakage
> problems. In the testing phase of RBWin, they're all complaining
> about how slow everything is. Of course, the one initial CONNECT
> takes about 5 seconds. There's a form based on a 1-row dummy table
> that can take 10 seconds to load. The application flies on a local
> drive. Again the main user form is brought up based on a primary
> key search, same thing -- can take 10 seconds to come up.
> Immediate if it's local.
>
> I went back and reread all the email I've been saving about this topic.
> There's no App.Exp so there's no extra connects around. I read
> about tweaking Norton AV settings (which I know they have) and will
> do that. I also read about a possible 'time out' fix
> (Net Config Server /autodisconnect:-1) so will try that too.
>
> Any other tips that people have found lately? Their network guys
> support other RBase clients, so are familiar with the product, and
> they point their fingers back at us.
>
>
> Karen
>
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
