Path: utzoo!attcan!uunet!clyde.concordia.ca!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!crdgw1!ge-dab!tarpit!bilver!bill From: bill@bilver.UUCP (Bill Vermillion) Newsgroups: comp.sys.amiga Subject: Re: CALL FOR LOCAL DISCUSSION: Split the c.s.a group more? Message-ID: <1107@bilver.UUCP> Date: 15 Oct 90 05:07:09 GMT References: <1990Oct6.051722.7143@zorch.SF-Bay.ORG> <63016@iuvax.cs.indiana.edu> Reply-To: bill@bilver.UUCP (Bill Vermillion) Organization: W. J. Vermillion - Winter Park, FL Lines: 36 In article <63016@iuvax.cs.indiana.edu> amhartma@silver.ucs.indiana.edu (Andy Hartman - AmigaMan) writes: >In article liberato@dri.com (Jimmy Liberato) writes: >> >>Second, the incidence of crossposting will increase dramatically. >Well, the overall volume of articles would go down on c.s.a. Okay - a comment from a non-Amiga user. I have many amiga users as readers on this system. This past week I have told them they are going to have to be choosier, because I had to shorten the expire on comp.sys.amiga. My system was complaining that the directories were too large. On this system, a 25mHz, 386 with a 15mb/sec ESDI drive, a read of a typical directory, long listing, comp.sys.sun for example comes up in 4 seconds. I just timed the comp.sys.amiga at 24 seconds. And that is after cutting down it's expire time to ONE THIRD all the other groups. When directory sizes get above 5000 bytes and you start going to double-indirect blocks it really slows down. The directory listing took over 90 seconds last week before I removed 2/3 of all the files and rebuilt the directory to get the overhead. As an SA I don't care what you discuss, but if you don't follow through with more groups, the local Amiga readers are going to have to go like hell to keep up with any news, because as the volume grows, the expires WILL get shorter. -- Bill Vermillion - UUCP: uunet!tarpit!bilver!bill : bill@bilver.UUCP