Re: Java thory and proctice: Garbase collection and performance
John Austin wrote: Isn't allocation the only unseen part of construction ? Everything else is visible in the code and surely a few assignments are never expensive. Any other expensive operations will stand out in measurements of code execution. That's correct. However, the article seemed to shout Don't worry about creating as much objects as you want, which I wouldn't support if taken literally. You are right that proper tools should uncover any additional overhead though. Moore's law is another optimization we sell in advance all the time. *bg* Twenty years ago, I had to work on a 8008 driven computer with 4k RAM and 12k ROM. That's enough to run a program which nicely prints formatted and justified text (25 lines a 80 characters). We went a lng way since then. J.Pietschmann
Re: Java thory and proctice: Garbase collection and performance
On Fri, 2004-02-20 at 15:46, J.Pietschmann wrote: *bg* Twenty years ago, I had to work on a 8008 driven computer with 4k RAM and 12k ROM. That's enough to run a program which nicely prints formatted and justified text (25 lines a 80 characters). We went a lng way since then. I went to a presentation on the Mars Rover's at the St John's GeoCentre which is one of the sites that NASA has granted access to the FTP site for fresh Images ... Comparing the old Mars projects to the new stuff ... That was FORTRAN ... This is Java. I recall hearing about a court case in which the Canadian Military were suing a supplier about something as trivial nowadays as 8K of memory. -- John Austin [EMAIL PROTECTED]
Re: Java thory and proctice: Garbase collection and performance
John Austin wrote: I noticed this artcle on Developer Works: Java theory and practice: Garbage collection and performance http://www-106.ibm.com/developerworks/library/j-jtp01274.html Something to read on Thursday. Nice read, however, they don't talk about constructors. There are still arguments for reusing objects and for trying to replace objects with a bunch of primitive values. (BTW a nice try selling yet-to-be-written optimizations regarding inlining...) J.Pietschmann
Re: Java thory and proctice: Garbase collection and performance
On Thu, 2004-02-19 at 17:53, J.Pietschmann wrote: John Austin wrote: I noticed this artcle on Developer Works: Java theory and practice: Garbage collection and performance http://www-106.ibm.com/developerworks/library/j-jtp01274.html Something to read on Thursday. Nice read, however, they don't talk about constructors. There Isn't allocation the only unseen part of construction ? Everything else is visible in the code and surely a few assignments are never expensive. Any other expensive operations will stand out in measurements of code execution. are still arguments for reusing objects and for trying to replace objects with a bunch of primitive values. (BTW a nice try selling yet-to-be-written optimizations regarding inlining...) Moore's law is another optimization we sell in advance all the time. -- John Austin [EMAIL PROTECTED]
Java thory and proctice: Garbase collection and performance
I noticed this artcle on Developer Works: Java theory and practice: Garbage collection and performance http://www-106.ibm.com/developerworks/library/j-jtp01274.html Something to read on Thursday. -- John Austin [EMAIL PROTECTED]
