From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20360 invoked by alias); 11 Jan 2004 07:45:26 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 20353 invoked from network); 11 Jan 2004 07:45:26 -0000 Received: from unknown (HELO garm.central.cmich.local) (141.209.15.48) by sources.redhat.com with SMTP; 11 Jan 2004 07:45:26 -0000 Received: from leon.phy.cmich.edu ([141.209.165.20]) by egate1.central.cmich.local with Microsoft SMTPSVC(5.0.2195.6713); Sun, 11 Jan 2004 02:45:24 -0500 Received: from localhost (unknown [127.0.0.1]) by leon.phy.cmich.edu (Postfix) with ESMTP id C1DAF7000B; Sun, 11 Jan 2004 02:45:19 -0500 (EST) Date: Sun, 11 Jan 2004 07:45:00 -0000 From: Eric McDonald To: Erik Jessen Cc: 'Jim Kingdon' , Subject: RE: HW requirements In-Reply-To: <000101c3d815$45825cb0$6401a8c0@Win2k> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 11 Jan 2004 07:45:24.0326 (UTC) FILETIME=[DF458060:01C3D816] X-SW-Source: 2004/txt/msg00056.txt.bz2 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