News for hackers. Stuff that matters.
Re:Erlang/OTP 17.0 has been released by derefr on Wednesday April 09, 2014 @03:26PM (#7561697)
Right, what I was asking in the second question is basically whether there exists, or is planned, a keyset cache to go along with the atom cache. I'd think that, if the atom cache is a good idea, a keyset cache would be good for exactly the same reasons.
Re:Erlang/OTP 17.0 has been released by jlouis on Wednesday April 09, 2014 @03:58PM (#7561930)
If you do that, it is better to create an arbitrary caching construction of subtrees and then reap the benefit by tighter packing of data in general. I agree a keyset cache could be really nice to have going forward. It would resemble what happens in-heap.

But the rule of the Ericsson OTP team is to get it correct before making it fast.

Re:Erlang/OTP 17.0 has been released by derefr on Wednesday April 09, 2014 @04:17PM (#7562049)
Atoms and keysets both have pretty much the same caching semantics, though: they get repeated over the wire with pretty good locality, and don't have conflicting terms busting the cache in-between. That's not really true for anything else, which makes me guess that an arbitrary term-branch cache would be pretty useless.
Re:Erlang/OTP 17.0 has been released by jlouis on Thursday April 10, 2014 @07:50AM (#7565329)
The idea of having arbitrary subtrees is to support an efficient compression scheme. But you are indeed right that a keyset cache would be extremely effective at limiting the size of maps.