An example is when there are a huge number of scalars having random contents. Here compressed storable has 33% over head, where as compressed json has 70%+ overhead. 
use strict;
use warnings;

use Storable;
use IO::Compress::Gzip qw(gzip);
use JSON::XS;

my (@data,$serial,$gzserial,$json,$gzjson,$i);

for($i=0;$i<100000;$i++) { push @data, chr(int(rand(256)))}

$serial = Storable::nfreeze(\@data);
$json = encode_json(\@data);

gzip \$json => \$gzjson;
gzip \$serial => \$gzserial;

print scalar(@data)."\n";
print length($serial)."\n"; 
print length($gzserial)."\n";
print length($json)."\n";
print length($gzjson)."\n";

[download]

In reply to Re^2: Serialise to binary? by Anonymous Monk
in thread Serialise to binary? by sectokia

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.