Re^15: Avoid Locking Entire Hashes

I haven't really gone over the list of changes.

I'm using ActivePerl build 1400 for x86.

My CPU is 2 years newer. And while the clock is slower, it has a "turbo" frequency of 2.8 GHz (whatever that means) which is faster. (Presumably, it speeds up when needed, saving power the rest of the time. This is a laptop CPU. M = Mobile)

Core i7 720QM
Core 2 Q6600

Comment on Re^15: Avoid Locking Entire Hashes

Replies are listed 'Best First'.
Re^16: Avoid Locking Entire Hashes by BrowserUk (Patriarch) on Jun 15, 2011 at 21:50 UTC
And while the clock is slower, it has a "turbo" frequency of 2.8 GHz Hm. Still, if this was down to just a faster cpu then I would have expected both methods to have been sped up roughly in equal proportion. The last set of numbers I posted were also for AS 1400, though 64-bit. I still am not seeing causality for the indirected scalar locking to be so expensive on my system. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]

Replies are listed 'Best First'.

Re^16: Avoid Locking Entire Hashes
by BrowserUk (Patriarch) on Jun 15, 2011 at 21:50 UTC

And while the clock is slower, it has a "turbo" frequency of 2.8 GHz

Hm. Still, if this was down to just a faster cpu then I would have expected both methods to have been sped up roughly in equal proportion.

The last set of numbers I posted were also for AS 1400, though 64-bit. I still am not seeing causality for the indirected scalar locking to be so expensive on my system.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]