Re: this == that

2006-05-02 Thread Tatu Saloranta
<[EMAIL PROTECTED]> wrote: > > > > karl wettin wrote: > > > The code is filled with string equality code > using == rather than > > > equals(). I honestly don't think it saves a > single clock tick as the > > > JIT takes care of it when the first lin

Re: this == that

2006-05-01 Thread Chris Hostetter
A couple of responses to various comments in this thread... : > Unless it object identity is what is being tested or intern is an : > invariant, I think it is dangerous. It is easy to forget to intern or to : > propagate the pattern via cut and paste to an inappropriate context. interning the St

Re: this == that

2006-05-01 Thread Yonik Seeley
On 5/1/06, jian chen <[EMAIL PROTECTED]> wrote: I am wondering if interning Strings will be really that critical for performance. Probably not as much as it was for early JVMs. The biggest bottle neck is still disk. Depends on the index and workload. Queries are often CPU-bound. -Yonik ht

Re: this == that

2006-05-01 Thread jian chen
lity code using == rather than > equals(). I honestly don't think it saves a single clock tick as the > JIT takes care of it when the first line of code in the equals method > is if (this == that) return true; If the strings are intern() then it should be a touch faster. If the string

Re: this == that

2006-05-01 Thread DM Smith
karl wettin wrote: The code is filled with string equality code using == rather than equals(). I honestly don't think it saves a single clock tick as the JIT takes care of it when the first line of code in the equals method is if (this == that) return true; If the strings are intern() th

Re: this == that

2006-05-01 Thread karl wettin
30 apr 2006 kl. 04.48 skrev Tatu Saloranta: JIT takes care of it when the first line of code in the equals method is if (this == that) return true; In case where (this == that) is true, this may well be correct, but: Please correct me if I'm wrong. ... you are then assuming 100%

Re: this == that

2006-04-29 Thread Tatu Saloranta
--- karl wettin <[EMAIL PROTECTED]> wrote: > The code is filled with string equality code using > == rather than > equals(). I honestly don't think it saves a single > clock tick as the > JIT takes care of it when the first line of code in > the equals method

this == that

2006-04-29 Thread karl wettin
The code is filled with string equality code using == rather than equals(). I honestly don't think it saves a single clock tick as the JIT takes care of it when the first line of code in the equals method is if (this == that) return true; Please correct me if I'm wrong. I can co