Re: beginning with ML

Vesa Karvonen wrote:
Note that just going to 64-bits doesn't necessarily improve
performance. On a 64-bit target, MLton uses 64-bit pointers, which
can increase memory pressure significantly, causing both more cache
misses and more time spent doing GC.

That problem would equally afflict OCaml.

--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?u
.

Relevant Pages

  • Re: beginning with ML
    ... On a 64-bit target, MLton uses 64-bit pointers, which ... causing both more cache ... misses and more time spent doing GC. ...
    (comp.lang.functional)
  • Re: C++: 64 bit performance vs. 32 bit
    ... There might be some workloads that benefit from all this work, but it seems like a high price to pay to reduce the cache impact of 64-bit pointers. ... the Linux kernel does something similar to what the OP asked. ... registers avoid would all be cache hits. ...
    (comp.arch)
  • Re: Code density and performance?
    ... "The time spent waiting for the transfer to start should be ... > MB/s disk transfer rate, then you're looking at about 512 KB transfer ... The thing about a page size is that it's obviously the smallest memory ... you can say that you don't care about mmap cache coherency: ...
    (comp.arch)
  • Re: Should we build i386 or i686 rpms?
    ... > James Wilkinson wrote: ... >> cache, slightly slowing things down. ... I don't have any AMD64 ... to pointers, longs, immediate constants, and some longer instructions. ...
    (Fedora)
  • Re: Cache Hit Ratio from system views
    ... indicator is how long business transaction take. ... but breaking down the response time into it's ... Time spent in application server ... "A low cache hit ratio does not imply that increasing the size of the ...
    (comp.databases.oracle.server)