Resurrecting an old thread.
I'm using gob to serialise very large data sets for storage rather than
message passing (maybe this is not an intended use - please suggest
other approach if this is the case - it seems like the best option at
this stage). Some cases leave me with gobs that are on the order of
On Sun, 2015-04-19 at 23:25 -0700, Egon wrote:
> What data?
> Can you give the data-structure(s)?
> How often do you read/write the whole data?
> Do you need random access to data?
Slices of named 4-tuples (struct of ints). Infrequent. Sequential.
On Mon, 2015-04-20 at 00:46 -0700, Egon wrote:
> Does the order matter?
No, not really.
> First I would change the Top/Bottom ... to int8, int16, int32, int64
> depending on what is needed.
> Then I would just mmap the whole structure to a file.
This is something I'd rather avoid. This is research software and is
subject to change. This is the reason I wanted to avoid encoding/binary.
Hmm. No reason - sounds like a bug/overnight. I will look into it next couple of days.
By the way, it would be great if you could expose a simpler CBOR encode/decode API.
Something more akin to, say, the json or gob ones.
err := cbor. NewEncoder(w).Encode(v)
I understand why your go/codec package exposes such a sophisticated API, but being able to just have a json/gob dropping one would be quite neat.
sent from my droid