Why not just a hash tied to a Berkeley DB database instead of messing with Storable and huge files?
#!/usr/bin/perl use warnings; use strict; use Carp; use File::Slurp; use BerkeleyDB; my %html_files; my $totalSize = 0; my $fileName = 'brick'; my $db = tie %html_files, 'BerkeleyDB::Hash', -Filename => $fileName, -Flags => DB_CREATE; die "can't open db: $!\n" if ! $db; opendir TD, '.' or croak $!; foreach my $file (readdir TD) { next if $file eq $fileName; my $fileData = read_file($file); $html_files{$file} = $fileData; $totalSize += length($fileData); } print "Stored $totalSize bytes\n"; exit 0; # 'good' exit for the shell

In reply to Re: Improving Memory Efficiency with Storable and Hashes of Scalars (code) by bikeNomad
in thread Improving Memory Efficiency with Storable and Hashes of Scalars (code) by deprecated

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.