Xref: utzoo comp.os.vms:4554 comp.protocols.tcp-ip:2466
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mcnc!ecsvax!tpmsph
From: tpmsph@ecsvax.UUCP (Thomas P. Morris)
Newsgroups: comp.os.vms,comp.protocols.tcp-ip
Subject: Need info on TWG TCP-IP processor overhead
Keywords: Wollongong TCP-IP TELNET VMS Overhead CPU
Message-ID: <4582@ecsvax.UUCP>
Date: 8 Feb 88 21:05:20 GMT
Organization: UNC Educational Computing Service
Lines: 23

Our site is looking into the purchase of some TCP-IP
terminal servers, to be connected to our VAX VMS 8530,
using the Wollongong TCP-IP (if we cannot find any
IVECS-type BI-bus processor board).

We have heard from other sites that there is `some'
overhead in running TCP-IP terminal server connections
using the TWG software. Claims about CPU overhead have
varied wildly. Can anyone who is actually using TWG
TCP-IP and VMS with BRIDGE or Micom or XYPLEX or DEVELNET
servers please comment? 

	"Hard" data would be much preferred. Something like
"The cpu overhead is x%/connected process" or "we find that
xx connections use yy% cpu just for communications via TCP-IP".

Thanx in advance. Please reply via mail. I'll summarize and
post back to the net.

Tom Morris UNC School of Public Health

BITNET:	TOM@UNCSPHVX
USENET: ...!mcnc!ecsvax!tpmsph