Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #6444

Re: baseline performance test using java ...

Show all headers | View raw

On 7/3/2011 2:45 PM, Patricia Shanahan wrote:
> On 7/3/2011 11:33 AM, Abu Yahya wrote:
>> On 7/3/2011 11:23 PM, lbrt chx _ gemale kom wrote:
>>
>>>>> ~ We have all learned we should avoid String(s) and use
>>>>> StringBuffer(s) or better yet StringBuilder(s) but there is
>>> ~
>>>> Er, no. Strings are great ...
>>> ~
>>> I (obviously) meant to say String(s) if you need to build them
>>> andStringBuilder(s)
>> > if you are working (most of us by now) on some multiprocessing core
>>> ~
>>
>> If you need to build them, you'd need a StringBuilder. And if you need
>> support for multiple threads AND need to modify them, you'd need a
>> StringBuffer.
>
> Often, the StringBuffer locking is not strong enough to be really
> useful. If, for example, a thread needs to append two strings to the
> buffer and have them appear consecutively in the resulting string, it
> needs synchronization at a higher level.

StringBuffer is better than StringBuilder in the case where
if >1 threads append N characters to it, then you are happy
if you get N characters appended don't care about the order.
That is practically never the case. The order of characters
is almost always significant.

Arne

Back to comp.lang.java.programmer | Previous | Next | Find similar

Thread

Re: baseline performance test using java ... Arne Vajhøj <arne@vajhoej.dk> - 2011-07-22 23:41 -0400

csiph-web