> -----Original Message----- > From: J.Pietschmann [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 01, 2003 2:43 PM > To: Jakarta Commons Developers List > Subject: Re: [math][functor] More Design Concerns > > > [EMAIL PROTECTED] wrote: > > I would steer away for primative as much as possible. > > Keep in mind that excessive object creation can and usually is > a significant performance drain, both because it is slow in itself > despite all kinds of optimization as well as causing more GC. > > J.Pietschmann >
Maybe this was a concern a few years ago but with the improvements to HotSpot and GC, these arguments against Java object creation have diminished in power. One of the biggest gains in GC performance has been with short-lived objects (the type of objects that commons-math would be creating and using) and effectively and efficiently allocating them in memory and releasing them. And with HotSpot, frequently executed pieces of code will actually start to increase in performance as a application runs longer, and in many occasions eclipse C or C++ performance. Here are a few interesting links about Java performance: http://java.sun.com/j2se/1.4/performance.guide.html http://servlet.java.sun.com/javaone/resources/content/sf2002/conf/sessions/p dfs/2583.pdf http://www.idiom.com/~zilla/Computer/javaCbenchmark.html http://www.visi.com/~khuber/java/JavaC.pdf Here's one article that's hard to fathom: http://www.javaperformancetuning.com/news/qotm028.shtml Brent Worden http://www.brent.worden.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
