On Mon, 13 Jun 2011, Christopher Howard wrote:
> I wasn't trying to say ur objections were purely philosophical. I was just trying to steer the conversation in a direction that was a little more helpful. When it comes down to it, i think we all agree that memory optimization is important. But what most serious problems that need to be addressed? E.g., in Firefox's case, what would u say are the biggest issues as far as memory consumption? Actual memory leaks? Caching pages too long? Too much functionality? Someone mentioned more efficient data structures, but how far can u really go with that? (E.g., a jpeg in memory really can't be compressed any more)
:-) I think I started this thread with that. If we can't get developers
to make system impact a high priority for their software than make them live
with their mistakes on older hardware. Completely unenforceable, and no one
will ever do it, but if they did do it, I'd wager they'd care a lot more.
Maybe we can make an uber cool group to entice people to join and deny
themselves the pleasures of modern hardware. The cloistered order of
Ascetics Programming for Efficent Systems (APES). :-)
On a more serious note us code monkeys simply have to make a personal
commitment to profile our applications not only for speed but for resource
utilization, and benchmark various approaches until we find a better balance
between the two. This means also double checking decisions to keep things
in memory for instant access that may be accessed infrequently enough to
make the carrying costs not worth while.
--Arthur Corliss
Live Free or Die
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Mon Jun 13 20:42:23 2011
This archive was generated by hypermail 2.1.8 : Mon Jun 13 2011 - 20:42:23 AKDT