Newsgroups: news.software.b Path: utzoo!henry From: henry@zoo.toronto.edu (Henry Spencer) Subject: Re: Painful interactive posting response from C news Message-ID: <1991Mar19.224659.4570@zoo.toronto.edu> Date: Tue, 19 Mar 1991 22:46:59 GMT References: <1991Mar11.181643.29880@zoo.toronto.edu> <1991Mar14.092311.20751@robobar.co.uk> Organization: U of Toronto Zoology In article <1991Mar14.092311.20751@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes: >In fact, I'm thinking of kludgeing it so that newsrun keeps a count of how >many batches its done, and after a limit, sleeping for a few minutes to >let sendbatches in (retaining LOCKinput, of course) then exiting or >continuing. Basically, just forcibly lower the duty cycle. > >Henry, is this unreasonable, or have you got a better idea ? Actually, in systems where news comes in compressed, there is already an effect much like this, since newsrun and friends take time off from holding down LOCK every time they have to decompress a batch. The obvious place to put code for a delay would be at the end of the outer loop, which runs 50 batches per iteration. This is worth considering; I'll take a look at it next time I'm working on the input subsystem. -- "[Some people] positively *wish* to | Henry Spencer @ U of Toronto Zoology believe ill of the modern world."-R.Peto| henry@zoo.toronto.edu utzoo!henry