linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Satchell <list@satchell.net>
To: ronkhu@ntsp.nec.co.jp
Cc: linux-c-programming@vger.kernel.org
Subject: Re: memory capacity
Date: Mon, 08 Dec 2003 16:51:42 -0800	[thread overview]
Message-ID: <1070931102.17309.11.camel@ssatchell1.pyramid.net> (raw)
In-Reply-To: <3FD454BB.7050005@hq.ntsp.nec.co.jp>

On Mon, 2003-12-08 at 02:38, ronkhu wrote:
> Can anyone help me in increasing the maximum allowable memory usage for 
> an application in HP/UX?
> 
> My superior instructed me to create an array of at least 7,140,000 
> elements(statically)... that would be able to
> store 8 bytes per index..
> 
> What compile option could i use to enhance the memory model (from small 
> to huge?) or increase the memory
> limit for an application?

So what is the limit currently?  I calculate the your array would
require 54.5 megabytes, and unless you have a VERY small swap store you
should be able to handle that easily on any modern computer with modern
operating system.  ("Modern" meaning less than four years old.)

Your other option is to learn how to do applications-level paging to
hard disk, so your RAM requirement is small -- I used to do such stuff
with minicomputers with 64 kilobytes without breaking a sweat.  By
breaking the data into fair-sized pages, you can have a decent working
set in a small footprint (512 KB if this is an old 286-based computer,
with 16-KB pages, as an example) and managing the page swapping
intelligenly, including doing some pre-sorting of input data to minimize
thrashing.

What are you going to do when those eight-byte records grow by a couple
of orders of magnitude?  Or you have to deal with multiple sets of
records in parallel?  You can't beat Parkinson's Law.

Satch



  reply	other threads:[~2003-12-09  0:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 10:38 memory capacity ronkhu
2003-12-09  0:51 ` Stephen Satchell [this message]
2003-12-09  1:35 ` Glynn Clements
2004-03-22 18:01   ` Splitter K.Anantha Kiran
2004-03-22  6:42     ` Splitter Jad Saklawi
2004-03-22 18:51       ` Splitter K.Anantha Kiran
2004-03-22  7:41         ` Splitter Jad Saklawi
2004-03-23  9:39           ` Splitter K.Anantha Kiran
2004-03-23 11:38             ` Splitter syedk
2004-03-23 11:54               ` Splitter K.Anantha Kiran
2004-03-23 13:31                 ` Splitter syedk
2004-03-25 19:35                   ` System hang at high bandwidth K.Anantha Kiran
2004-03-27 18:11                     ` Jan-Benedict Glaw
2004-04-06 14:20                   ` Can i use dev_queue_xmit K.Anantha Kiran
2004-04-06 16:55                     ` Armen Kaleshian
2004-03-22 19:30         ` Splitter Michael Taylor
2004-03-22 18:42     ` Splitter K.Anantha Kiran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1070931102.17309.11.camel@ssatchell1.pyramid.net \
    --to=list@satchell.net \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=ronkhu@ntsp.nec.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).