chuck@mitlns.mit.edu (01/16/90)
-Message-Text-Follows- How long should it take to SKIM remote served news groups? I'm trying to get Version 5.9c running with WINTCP under VMS 5.2. With a remote unix machine as server for all groups. I can "ping" the machine with results of 20-30ms. Getting articles works fine. But doing a SKIM to update the header list takes 10-20 minutes PER GROUP. Also ftp/telnet to the machine work well. What can be wrong? Chuck Parsons chuck@mitlns.mit.edu chuck@mitlns.bitnet P.S. Thanks for any help!
gih900@CSC.DNET (Geoff Huston) (01/22/90)
>How long should it take to SKIM remote served news groups? I'm trying >to get Version 5.9c running with WINTCP under VMS 5.2. With a remote >unix machine as server for all groups. I can "ping" the machine with >results of 20-30ms. Getting articles works fine. But doing a SKIM to >update the header list takes 10-20 minutes PER GROUP. Also ftp/telnet >to the machine work well. > > What can be wrong? > Chuck Parsons The problem lies in the implementation of news on the remote side - with Bnews nntp queries such as NEWNEWS cause the remote end to read the text of some (or in some cases all) stored item files in order to obtain the requested information. I have noticed that Cnews is somewhat faster as much of the required information is lifted out into db files in much the same approach as I used in the VMS implementation, and nntp responses can be formed quickly without the processing overhead. Certainly it is faster to run the server on VMS and have Unix clients than the reverse configuration in a mixed LAN environment. Geoff Huston