|
Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> helped spread the news by saying: > Fat, maybe. Obese, no. To me, a 26meg zip file for a "client" that > expands to 45meg on disk seems excessive. I would have a tough time > requiring that customers install this, if I wanted to use this to > communicate with them. Assuming they are iNation members, of course. > > BTW, I noticed, in Task Manager (XP Pro) that this thing bounces > between 2% and 6% CPU utilization - it's constantly chugging away in > what, to me, seems a fairly intensive manner. And that does not > include popping up alerts. > > Regards > > Vern > > At 09:00 PM 2/20/2003 -0500, you wrote: >>I misunderstood. Thank you for sorting me out. >> >>It leads to the next question though: I do not understand why "A 26MB >>RAM footprint" is a bad thing. Isn't RAM to be used? >> >> (I do understand the concept of Hog, but with the low price of >> memory, is >>it wise to spend a lot of energy in making applications thin? >> >>--------------------------------------------------------- >>Booth Martin http://www.MartinVT.com >>Booth@xxxxxxxxxxxx >>--------------------------------------------------------- Vern, I think that's the nature of the JRE, isn't it? I notice the same thing when using CodeEdit, CodeDsu, CodeProj, etc... Or maybe it's just the nature of instant messengers? We run a "home- grown" Win32 app internally to communicate. It uses (typically) 15Mb (snort, snort!) and about 2% of the CPU. Must just be the constant, "I'm here, got anything for me?" queries going out... And as far as 26Mb expanding to 45... Have you SEEN the WDSC tools from IBM? The older ones (I'm using CodeEdit instead of Eclipse) take close to 600 Mb! -- David Schopp WISDM Team Leader Computers Unlimited
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.