Q: too much data too little memory
From: Fei Chen (feic@stats.ox.ac.uk)
Date: 04/17/03
- Next message: Kevin R.: "Re: installing NEDIT on Cygwin and unix in general"
- Previous message: Andrew Gabriel: "Re: Solaris 5.5.1: Questions on shared memory and the ipcs program"
- Next in thread: Fletcher Glenn: "Re: too much data too little memory"
- Reply: Fletcher Glenn: "Re: too much data too little memory"
- Reply: phil-news-nospam@ipal.net: "Re: Q: too much data too little memory"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Fei Chen <feic@stats.ox.ac.uk> Date: Thu, 17 Apr 2003 13:30:16 +0100
Dear all,
Advanced appologies if this turns out to be a trivial question.
I was wondering, with a large chunk of data that does not fit into all the
physical memory available to a computer, is it better, to run one process
that attempts to load all the data, and thus off loading the memory
management work to the OS (e.g. via paging/swapping). Or is it better to
start several processes concurrently, each of which takes in a chunk of
data that individually does fit into memory, and thus have the OS manage
these processes. Or there is really little difference between these two
approaches?
Thanks for any pointers,
Fei Chen
- Next message: Kevin R.: "Re: installing NEDIT on Cygwin and unix in general"
- Previous message: Andrew Gabriel: "Re: Solaris 5.5.1: Questions on shared memory and the ipcs program"
- Next in thread: Fletcher Glenn: "Re: too much data too little memory"
- Reply: Fletcher Glenn: "Re: too much data too little memory"
- Reply: phil-news-nospam@ipal.net: "Re: Q: too much data too little memory"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
Loading