"Chris Thomasson"
news:yoGdnc1ctO5EWZ_VnZ2dnUVZ_jWdnZ2d@comcast.com...
> "Razii"
> news:sef504dd3e8nqu3laq0otc3m5ed04tv28s@4ax.com...
>> On Sun, 13 Apr 2008 21:02:43 -0500, Razii
>>
>>
>>>It's not working...When I run it, I get
>>>
>>>(00473118/19862)-Cache Prime
>>>(00473128/19863)-Cache Prime
>>>(snip)
>>>(00FCF9B8/250000)-Cache Overflow
>>>(00FCF9F8/250000)-Cache Overflow
>>>(snip}
>>>(01B31518/0)-Cache Miss!
>>>(01B31528/0)-Cache Miss!
>>>(01B31538/0)-Cache Miss!
>>>(01B31548/0)-Cache Miss!
>>>(01B31558/0)-Cache Miss!
>>>(snip)
>>
>> Never mind. Why leave all printfs in the benchmark version? Anyway..
>>
>> Time: 26875 ms
>>
>> Not much improvemnt.
>>
>> peak memory was 60 MB.
>
> Okay. That's what I expected. I am going to play around with this and see
> if I can get somewhere near the Java version. Thanks for your patience.
>
> ;^)
One comment on 'System.go()':
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/System.html#gc()
This is basically only a "strong suggestion" that the JVM runs a collection.
Java could basically say, na, I don't need to run a collection cycle at this
time; it knows better that the programmer most of the time. Is there any way
to know for sure if Java actually runs a gc cycle?