cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Washeim <esa...@canuck.com>
Subject Re: Check this!
Date Thu, 17 Feb 2000 19:50:43 GMT
StringBuffer is less resource hungry (object creation wise) than String. Use
stringbuffers.

on 17/2/2000 18.00, COFFMAN Steven at SCoffman@CBSINC.com wrote:

>> From the article:
> "Among these pitfalls are the excessive use of strings, which in the Java
> language are immutable objects, and excessive use of exceptions"
> 
> Each time you modify a String ("Hello" to "olleH") you basically create a
> new object and recycle the old one. I see how this is less efficient then
> merely modifying the bytes in a previously allocated array of characters,
> but what alternative is there in Java? FOP uses StringBuffer all over the
> place, but I thought that was *worse* than String. Are Java arrays of chars
> better? 
> 
> -----Original Message-----
> From: PNarula@directsourcing.com [mailto:PNarula@directsourcing.com]
> Sent: Thursday, February 17, 2000 10:44 AM
> To: fop-dev@xml.apache.org; cocoon-dev@xml.apache.org
> Subject: Check this!
> 
> 
> Check this article! It is worth reading.
> 
> SanFrancisco performance A case study in performance of large-scale Java
> applications
> http://www.research.ibm.com/journal/sj/391/christ.html
> <<SanFrancisco performance A case study in performance of large-scale Java
> applications.url>>
> 

-- 
Mark (Poetaster) Washeim

'In Xanadu did Kublai Khan
 A stately pleasure dome decree . . .'

 



Mime
View raw message