daemon@ucbvax.BERKELEY.EDU (The devil himself) (06/05/86)
We are running Kermit-32 v3.2.077 on a DEC VAX-11/750 under VMS v4.3, dialing out at 1200bps via a DMF-32. All the functionality that I have used works fine so far, and I am reasonably satisfied with Kermit's behavior when SENDing or GETting files while relating to a server. It works fine as a server itself. However, when I am in CONNECT mode as an outbound interactive terminal talking to another system, and the other system fills my screen (e.g., reading news), I find my process doing an amazing amount of buffered I/Os, and taking up as much CPU as I can throw at it - like up to 85-95% of a system that was already moderately to heavily loaded. All other user processing and I/O virtually stops until I stop receiving characters. I can watch other screens stop painting until mine is done. And this with the outbound link at 1200bps! Wanting to share in a friendly manner with the rest of the users (:-), have I any recourse besides lowering my process priority upon entering Kermit? If I drop to 2 (normally everyone is at 4), my screen-filling starts looking a little bursty but everyone else is getting better service. What effect do things like TTY_BUF, TTY_TYPAHDSZ, TTY_ALTYPAHD, TTY_ALTALARM, TTY_DMASIZE, and the like have on this situation? Where else should I be looking? Or is Kermit-32 inherently this grabby with IOs and CPU time? --Bob Sutterfield OCES VAX System Manager IRCC Facilities Management The Ohio State University bob%osuag.uucp@ohio-state.arpa