comment on

Zaxo,
This is very similar to the idea I had. I discovered that compiling the offsets using DBM::Deep was extremely slow, but was fast for subsequent runs. This also has the advantage of not requiring the dictionary file to be sorted.

#!/usr/bin/perl
use strict;
use warnings;
use DBM::Deep;

open(my $dict, '<', 'words.raw') or die "Unable to open 'words.raw' fo
+r reading: $!";

my $db = DBM::Deep->new("offsets.db");
build_db($db, $dict) if ! scalar keys %$db;

for my $char ('a' .. 'z') {
    for (1 .. 100) {
        print get_rand_word($db, $char, $dict);
    }
}

sub build_db {
    my ($db, $dict) = @_;
    my $pos = tell $dict;
    while ( <$dict> ) {
        my $char = substr($_, 0, 1);
        push @{$db->{$char}}, $pos;
        $pos = tell $dict;
    }
}

sub get_rand_word {
    my ($db, $char, $dict) = @_;
    my $offset = $db->{$char}[rand @{$db->{$char}}];
    seek $dict, $offset, 0;
    my $word = <$dict>;
    return $word;
}
[download]

Other options include Storable and DBD::SQLite if a real RDBMS isn't available.

Cheers - L~R

In reply to Re^2: improving the efficiency of a script by Limbic~Region
in thread improving the efficiency of a script by sulfericacid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks