Comment on

If you don't mind reading the source file twice and a whole lot of random seeks the second time through, you can generate a list of offsets, shuffle those and then loop through a seek, read, write cycle:

#!/usr/bin/perl

use strict;
use warnings;
use List::Util qw(shuffle);

my @offsets;

print STDERR "Scanning...";

open(IN, $ARGV[0]);
do { push @offsets, tell(IN) } while (<IN>);
close(IN);
pop @offsets;

print STDERR "Done. ($#offsets)\nScrambling...";

@offsets = shuffle(@offsets);

print STDERR "Done.\nWriting scrambled...";

open(IN, $ARGV[0]);
for (@offsets) {
    seek(IN, $_, 0);
    my $line = <IN>;
    $line .= $/ if $line !~ qr{$/};
    print $line;
}

print STDERR "Done.\n";
[download]

This scrambled an 800k line/60M file I had handy in eight seconds with minimal memory usage in process space. I assume the kernel kept the entire file cached in memory.

In reply to Re: mem usage by crag
in thread mem usage by halfcountplus

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, 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, 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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


Pathologically Eclectic Rubbish Lister
	PerlMonks