> Ger Hobbelt wrote:
> Odd question maybe, but does the API call slowdown too when traversing
> other heaps (which carry fewer items)?
Yes. This surprised me, but Heap32Next takes the same amount of time
to execute when traversing the 2nd heaplist (which has 15 items) as it
does the 1st heaplist
I've confirmed my linear performance conjecture w/r/t heap objects.
Click here to see pretty pictures graphing my results:
http://thenewjamesbaker.blogspot.com/2009/11/performance-of-heap32next-on-64-bit.html
On Thu, Nov 12, 2009 at 11:50 AM, James Baker wrote:
> Punchline: The time ta
2009 at 4:50 PM, James Baker wrote:
> It's not the CryptoAPI calls that are taking time - nearly all of the
> time is spent within Heap32Next. Thus my hypothesis is that
> CryptAcquireContextW or CryptGenRandom is failing, causing 'good' to
> be 0 and the heap traversa
t
> process is retrieved. Can you exactly specify which CryptoAPI is taking so
> much time?
> -Sandeep
>
> On Fri, Nov 6, 2009 at 11:45 AM, James Baker wrote:
>>
>> Background: Testing a Ruby app on 64-bit Windows 7 Ultimate, I found
>> that OpenSSL::PKey::RSA.gen
