unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: amusing CoW string dedupe example
Date: Thu, 11 Jun 2020 19:39:21 +0000	[thread overview]
Message-ID: <20200611193921.GA17563@dcvr> (raw)

I've always known hash keys get deduplicated in Perl to save RAM
for a while; but it turns out that it's possible to (ab)use them
for dynamic strings even when the hash doesn't live beyond a
subroutine scope.

Looks like we'll be able to save RAM in some places :D

The following script takes between 5-9M of RAM depending on the
version of Perl I'm using (tested down to 5.16.3), but nearly 1G
if the early return is uncommented in the `dedupe' sub:

----8<----
#!perl -w
use strict;
use Devel::Peek;
sub dedupe {
	my ($k) = @_;
#return $k; # uncomment to disable CoW dedupe, needs ~1G of RAM
	my %cow = ( $k => undef );
	((keys %cow)[0]);
}

my $n = 3_600_000;
my $k = pack('S*',($n + 1)..($n + 50000)); # uint16_t array[50000]
my @x = map { dedupe($k) } (1..10000);

{
	no warnings 'once';
	$Devel::Peek::pv_limit = 10;
}
Dump(\@x);
print 'length: ',length($k), "\n";

                 reply	other threads:[~2020-06-11 19:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200611193921.GA17563@dcvr \
    --to=e@yhbt.net \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).