Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Storable CPAN distribution.

Report information
The Basics
Id: 2525
Status: new
Priority: 0/
Queue: Storable

Owner: Nobody in particular
Requestors: simonhf [...]

Bug Information
Severity: Wishlist
Broken in: 2.07
Fixed in: (no value)

Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.405 (Entity 5.404)
Subject: Suggestion for optimizing binary dump size
X-RT-Original-Encoding: iso-8859-1
Content-Length: 656
Download (untitled) / with headers
text/plain 656b
I've been experimenting with dumping large hashes in ascii and binary (using Storable) format. I noticed that, although the binary dumps are about twice the speed of ascii dumps, the binary files are only about 10% smaller than their ascii counterparts. On closer examination of the binary dump files then I noticed that the storage of hash keys is not optimized to save space. For example, if I have 500 keys called "CUSTOMERID" then the string "CUSTOMERID" will appear 500 times in the binary dump file. It would be great to have a Storable option which, when selected and a hash is being dumped, analyses key usage on-the-fly and stores keys only once.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to