Efficiency of gob mapping

[bsr]

Hello,

I use code similar to 

http://play.golang.org/p/YQr-DeeWGL

for mapping and persisting complex structure to database.

How inefficient is it? I am not sure anyway to optimize (not sure reuse buffer etc make difference or cause any issue). Please give any suggestion to improve it.

thanks

[John Asmuth]

Encoding to gob is faster than writing it to a disk, so you probably don't need to worry about it.

[rif]

For me it was to slow (it is better to be used with larger streams of data). I ended up writing my own encoder/decoder for my structures.

[Rob Pike]

The gob package does a lot of work the first time it sees a type to
encode/decode on a given encoder/decoder. In effect, it builds a
little JIT. Once that's built it's reasonably efficient if there's
lots of data, but there is a modest constant-time overhead. Your
example contains nothing to encode (the structs are empty) so it's not
a realistic example upon which to base any decision about performance.

-rob