On Mon, 15 Dec 2003 19:38, you wrote: > I also assumed at first that your kids were annoyed because of > performance of the cpu taken up by the emerge compilation process. Now > it appears I was wrong, its the downloads afecting online games. > > Ok well how about speed limiting the wget command in portage? the > download command can be specified in /etc/make.conf, and wget has a rate > limiting option. > > RTFM for more details :-) Se below too.
> Nick > > > On Mon, > 15 Dec 2003 17:13:19+1300"Fisher, Robert(FXNZ > > CHC)"<[EMAIL PROTECTED]> wrote: > > Truth is I usually try to change the router to point to jetstreamgames > > and then.... > > > > emerge -uf world && emerge -u world > > > > Works a treat. > > > > For non Gentoo users - this downloads all of the files first (really > > fast) then I can change the router back to normal while the > > compilation takes place. > > > > Robert > > > > Experience is something you don't get until just after you need it. > > > > -----Original Message----- > > From: Fisher, Robert (FXNZ CHC) [mailto:[EMAIL PROTECTED] > > Sent: Monday, 15 December 2003 5:04 p.m. > > To: '[EMAIL PROTECTED]' > > Subject: RE: Nice > > > > Ed Zachery! > > > > (see my previous answer) > > > > Rob > > -----Original Message----- > > From: Michael JasonSmith [mailto:[EMAIL PROTECTED] > > Sent: Monday, 15 December 2003 4:58 p.m. > > To: linux users > > Subject: Re: Nice > > > > On Mon, 2003-12-15 at 16:40, Christopher Sawtell wrote: > > > su - > > > Password: secretblah > > > nohup nice 18 emerge --update package 2&1> ~/emerge.log & > > > logout > > > > > > The update will now take place in the backgound at a very low > > > priority, and probably won't even be noticed. > > > > Really? I would imagine that downloading many MB of data would not be > > very CPU intensive, so altering the "nice" level would not have a > > dramatic affect on the performance of the machine. > > > > The kids problem is this, if I understand correctly: > > 1. "emerge" is scheduled. > > 2. "emerge" requests a heap of data from the server. > > 3. The kernel puts "emerge" into interruptible-sleep state (D) > > until the data has arrived. > > 4. The pipe fills with data coming in from the server. > > 5. No...bandwidth...left...for...UT. Much...lag. Getting... > > fragged...lots...damn...you...Dad! > > Altering the "nice" level only affects how frequently (1) occurs, > > while the real problem is (4), which still happens far too frequently > > for the kids to be happy. > > > > There is a solution to their problem. I think it is called "bandwidth > > shaping" but I am not too sure of its name or how to do it\ldots TFM to R is the kernel help file. He say:- QoS and/or fair queueing (NET_SCHED) When the kernel has several packets to send out over a network device, it has to decide which ones to send first, which ones to delay, and which ones to drop. This is the job of the packet scheduler, and several different algorithms for how to do this "fairly" have been proposed. If you say N here, you will get the standard packet scheduler, which is a FIFO (first come, first served). If you say Y here, you will be able to choose from among several alternative algorithms which can then be attached to different network devices. This is useful for example if some of your network devices are real time devices that need a certain minimum data flow rate, or if you need to limit the maximum data flow rate for traffic which matches specified criteria. This code is considered to be experimental. To administer these schedulers, you'll need the user-level utilities from the package iproute2+tc at <ftp://ftp.inr.ac.ru/ip-routing/>. That package also contains some documentation; for more, check out <http://snafu.freedom.org/linux2.2/iproute-notes.html>. This Quality of Service (QoS) support will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router if you also say Y to "QoS support", "Packet classifier API" and to some classifiers below. Documentation and software is at <http://diffserv.sourceforge.net/>. If you say Y here and to "/proc file system" below, you will be able to read status information about packet schedulers from the file /proc/net/psched. The available schedulers are listed in the following questions; you can say Y to as many as you like. If unsure, say N now. Is that what you were thinking of? Id be interested to know how you get on with this as I have similar issues. -- C. S.
