Containers and strictness
johan.tibell at gmail.com
Thu Jun 24 08:27:54 EDT 2010
On Thu, Jun 24, 2010 at 1:59 PM, Edward Kmett <ekmett at gmail.com> wrote:
> 2010/6/24 Milan Straka <fox at ucw.cz>
> > On 24 June 2010 11:14, Milan Straka <fox at ucw.cz> wrote:
>> > > I need some opinion:
>> > >
>> > > - Do you think methods like insert/lookup/delete/etc should be strict
>> > > key/element?
>> > >
>> > > As Claus wrote, right now it is undocumented and inconsistent (both
>> > > the methods of one container and also in the same methods of
>> > > container).
>> > Just as it is sometimes important to be able to do strict inserts, it
>> > is important sometimes that we have maps that are lazy in the
>> > elements. There are important use cases both ways.
>> > So yes we should have some kind of consistent convention. We could do
>> > worse than the naming convention where the strict versions use a
>> > trailing prime ' character.
>> I thought we are talking only about keys/elements. I would leave the
>> values untouched.
>> Personally I vote for:
>> - keys in Maps and elements in Sets are strict
>> - vales in Maps are left untouched (lazy)
> +1 from me
> Great work so far.
The space overhead per key/value pair is 6 words (48 bytes on a 64-bit
architecture) when using lazy values but only 4 words (32 bytes) per
key/value pair when using strict (unpacked) values, a 50% difference. This
really starts to matter with big enough data sets (as seen in the recent
Twitter analysis thread). When work with Big Data it's often desirable to
fit as much data in RAM as possible as the result of many algorithms (think
machine learning or search ranking) differs with the amount of data you can
hold in memory.
Something to consider.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libraries