 
| Sender: |
|
| Date: |
Mon, 3 Jan 2011 18:01:20 -0500 |
| MIME-version: |
1.0 (Apple Message framework v936) |
| Reply-To: |
|
| Content-type: |
text/plain; charset=US-ASCII; format=flowed; delsp=yes |
| Subject: |
|
| From: |
|
| In-Reply-To: |
|
| Content-transfer-encoding: |
7bit |
| Parts/Attachments: |
|
|
On Jan 3, 2011, at 4:31 PM, Matt L. Miller wrote:
> It boggles my
> mind that any structure that (I assume) uses arrays to back it is
> faster
> than direct access to an array; how often does that happen?
I'm guessing it's a memory fence issue on compiling of some sort. At
any rate, it appears that if you have an array as an instance variable
in YOUR class, then accessing it in a method is faster
than someone externally accessing it even if it's public. At least in
Java 1.6, HotSpot, OS X. Anyway, seriously, in the goofy little
microbenchmarks I've written that's exactly what I'm seeing.
ArrayList can now sometimes be faster than accessing Bag's array
directly.
Sean
|
|
|
