Xref: utzoo comp.arch:11149 comp.sys.mips:122 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!asuvax!mcdphx!udc!chant!aglew From: aglew@urbana.mcd.mot.com (Andy-Krazy-Glew) Newsgroups: comp.arch,comp.sys.mips Subject: Re: Memory utilization & inter-process contention Message-ID: Date: 25 Aug 89 03:35:13 GMT References: <3332@blake.acs.washington.edu> <1989Aug22.163100.25540@utzoo.uucp> Sender: aglew@urbana.mcd.mot.com Organization: Work: Motorola MCD, Urbana Design Center; School: University of Illinois at Urbana-Champaign Lines: 12 In-reply-to: henry@utzoo.uucp's message of 22 Aug 89 16:31:00 GMT >Have you ever figured out how long it takes to swap out a 25MB process? >Or to swap it back in again? The fact is, this example system simply >does not have enough main memory for its workload. The fix is, either >double the memory or run the jobs in sequence rather than simultaneously. Isn't that what the scheduler is supposed to figure out by itself? -- Andy "Krazy" Glew, Motorola MCD, aglew@urbana.mcd.mot.com 1101 E. University, Urbana, IL 61801, USA. {uunet!,}uiucuxc!udc!aglew My opinions are my own; I indicate my company only so that the reader may account for any possible bias I may have towards our products.