On Thu, 16 Mar 1995 17:13:44 EST Wayne T. Smith said:
>Just because I know someone will try it if we sell ADSM service w/i
>the University System, I installed the Windows client (latest one -
>with compression fix) on my Windows 3.1(1?) system at home.
>To more complete the picture, I'm running DOS 6.0 and Norton Desktop
>for Windows and the connection to a VM server is a 14.4 modem with
>SLIP. The serial port is running at 19.6, since at higher speeds
>(Trumpet) Winsock (2) has severe problems. No other Winsock
>applications show any problem. This is a 486-33.
>The backup client starts as expected and zooms through the 1st 35
>files (according to the display), at which time it goes into
>slow-motion. After increasing the VM server timeout from 1 minute
>to 3 minutes and then again to 10 minutes, backup proceeds ... at a
>crawl. ADSM reports 0.125KB/sec, but it doesn't seem that fast. :(
>The modem transmit/receive lights *rarely* light. The PC acts
>sluggishly as if ADSM is in the background eatly cycles. ADSM acts
>this way whether there are other applications running or not, and
>specifically other Winsock applications or not.
>Is there a fix? Does anyone suspect my machine, Trumpet Winsock or
>SLIP, or what?
>Thanks for any light anyone might shed,
Well, I've had a lot of experience with a Mac at home and a little with
a co-workers PC. We're running with 28.8K (V.34/V.42bis) and PPP and
don't have any problems. The Mac and PC both average out around
2.6-2.9K/sec for transfer rates. The PC is running Windows 3.1 and is
a 486/66. We have compression set on due to the low transfer rate.
A hangover from when we were at 14.4K and no compression on the modems.
We haven't tried to see if ADSM or V42.bis alone is faster.
We don't see more than a delay of a couple of seconds on the server
side waiting for data and the SD/TR lights on the modem while not
constant keep right on blinking. The PC is running the Trumpet Winsock,
the 2.0b version (I think from the last supported winsock listing only
the 1.0 version is supported though). We did have some initial problems
similiar to what you are describing for slow transfers rates but that
was due to having the Xyplex PPP servers on a much to crowded ethernet
segment, for some obscure reason only ADSM and FTP were heavily trashed
by it though but, he says he never saw the sluggishness you describe
from your PC, his was still responsive, he was playing games while it
slowly ground away. He doesn't remember what release level he's running
right now though.
One thing we have both noticed is that it's not a continous data stream
from the client to the server. ADSM seems to do a disk read, then
compress the data, then send it, or so it seems to us anyway. This
may just be the case with compression of course, without compression
there may be a more continous data stream. If that's the way it's
actually working, it wouldn't surpise me to see a performance increase
in the future by multi-threading of these operations so that there is
always data ready and stacked waiting to send.
---
Keith A. Crabb Keith AT UH DOT EDU
Keith A. Crabb Keith AT UH DOT EDU
University of Houston Operating Systems Specialist +1-713-743-1530
|
