From: "Erik Jessen" <ejessen@adelphia.net>
To: "'Eric McDonald'" <mcdonald@phy.cmich.edu>
Cc: "'Jim Kingdon'" <kingdon@panix.com>, <xconq7@sources.redhat.com>
Subject: RE: HW requirements
Date: Sun, 11 Jan 2004 07:52:00 -0000 [thread overview]
Message-ID: <000201c3d819$0bcd93f0$6401a8c0@Win2k> (raw)
In-Reply-To: <Pine.LNX.4.44.0401110232110.25159-100000@leon.phy.cmich.edu>
My home machines all have at least 512MB RAM.
(have to - my kid's games want at least that much... I should go write
kid's games that suck up a lot of RAM, and buy stock in Micron, so I
make
all my money off the memory that people will buy to play the games ;)
At work we use 1-12GB RAM, but that's because we have to.
I really appreciate you doing the packed Boolean tables; it makes a big
difference to people with less memory. (maybe we should think about
Xconq on PalmPilot or Cellphones? Games on those things seem pretty
popular ;> )
Regards,
Erik
-----Original Message-----
From: Eric McDonald [mailto:mcdonald@phy.cmich.edu]
Sent: Saturday, January 10, 2004 11:45 PM
To: Erik Jessen
Cc: 'Jim Kingdon'; xconq7@sources.redhat.com
Subject: RE: HW requirements
On Sat, 10 Jan 2004, Erik Jessen wrote:
> So, is anybody even really considering HW resources when actually
doing
> development? (other than the general rule of "don't be wasteful")?
Well, that's the rule I follow. I try to be as conscious of memory
and execution efficiency as possible without writing code that
is too convoluted.
Since I may be adding some more tables of precomputed values soon,
I recently implemented packed boolean tables. On machines with
32-bit ints, this means using 1/32 the amount of memory that one
might otherwise use with 1 bool per int. (Bit vectors can easily
be created from this implementation, since they are simply 1 by n
or n by 1 packed boolean tables.)
That said, it is hard for me to "feel the pain" when it comes to
memory crunches, as the machine I use for development has 1 giga_,
I mean, gibibyte of memory. I suppose, for testing purposes, I
could lie to the Linux kernel about how much memory I have by
giving it a mem=64 argument from the boot loader or something....
Eric
next prev parent reply other threads:[~2004-01-11 7:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 2:40 New Action: change-type Eric McDonald
2004-01-07 2:47 ` Erik Jessen
2004-01-07 3:30 ` Eric McDonald
2004-01-07 2:51 ` Lincoln Peters
2004-01-07 4:04 ` Hans Ronne
2004-01-07 4:31 ` Eric McDonald
2004-01-07 20:08 ` klaus schilling
2004-01-07 20:17 ` Eric McDonald
2004-01-07 20:26 ` Hans Ronne
2004-01-07 20:47 ` Eric McDonald
2004-01-07 21:22 ` Eric McDonald
2004-01-08 6:28 ` Erik Jessen
2004-01-08 16:26 ` Eric McDonald
2004-01-10 5:49 ` Erik Jessen
2004-01-10 16:42 ` Eric McDonald
2004-01-10 17:57 ` Hans Ronne
2004-01-10 18:59 ` HW requirements Erik Jessen
2004-01-10 19:44 ` Hans Ronne
2004-01-10 23:31 ` klaus schilling
2004-01-11 0:25 ` Erik Jessen
2004-01-11 3:44 ` Jim Kingdon
2004-01-11 7:25 ` Erik Jessen
2004-01-11 7:45 ` Eric McDonald
2004-01-11 7:52 ` Erik Jessen [this message]
2004-01-11 21:19 ` Jim Kingdon
2004-01-11 0:31 ` Hans Ronne
2004-01-08 3:48 ` New Action: change-type Hans Ronne
2004-01-08 4:28 ` Eric McDonald
2004-01-08 6:39 ` Hans Ronne
2004-01-08 16:46 ` Eric McDonald
2004-01-11 16:48 HW requirements Feneric Brown
2004-01-11 17:02 ` Erik Jessen
2004-01-13 10:42 ` Bruno Boettcher
2004-01-11 16:52 Feneric Brown
2004-01-11 18:10 Feneric Brown
2004-01-11 20:05 ` Jim Kingdon
2004-01-11 18:12 Eric W. Brown
2004-01-12 17:19 ` Eric McDonald
2004-01-13 15:59 Eric W. Brown
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='000201c3d819$0bcd93f0$6401a8c0@Win2k' \
--to=ejessen@adelphia.net \
--cc=kingdon@panix.com \
--cc=mcdonald@phy.cmich.edu \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).