OK, we still miss some of the details, but let's have some fun.
I created a Makefile like this:
SHELL = /bin/bash
.PHONY: data
data:
for i in {1..10} ; do for j in {1..10} ; do echo "[$$i,$$j,$$RANDO
+M]" > $$i-$$j.json ; done ; done
.PHONY: simulate_cron
simulate_cron: data
while : ; do \
i=$$((1 + RANDOM % 10)) ; j=$$((1 + RANDOM % 10)) ; echo "[$$i
+,$$j,$$RANDOM]" > tmp ; mv tmp $$i-$$j.json ;\
done
.PHONY: query
query:
time perl query.pl
.PHONY: clean
clean:
rm -f *.json
Now, you can run
make simulate_cron
to generate the input data and start modifying them randomly.
Then, run
make query
in a different terminal. The Perl program is the following:
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };
use Cpanel::JSON::XS qw{ decode_json };
my %cache;
for (1 .. 1000) {
my @queries = map [ map int 1 + rand 10, 1, 2 ], 1 .. 50;
for my $query (@queries) {
my ($x, $y) = @$query;
# delete $cache{$x}{$y}; # <- Uncomment to simulate no cache.
my $value;
if (exists $cache{$x}{$y}
&& (stat "$x-$y.json")[9] == $cache{$x}{$y}{last}
) {
$value = $cache{$x}{$y}{value};
} else {
open my $in, '<', "$x-$y.json" or die $!;
$cache{$x}{$y}{last} = (stat $in)[9];
$value = $cache{$x}{$y}{value} = decode_json(do { local $/
+; <$in> })->[2];
}
say "$x, $y: $value";
}
}
With the delete line uncommented, it takes about 0.400s to terminate. With the line commented, it runs under 0.100s, i.e. slightly more than 4 times faster.
Notes:
- The simulation uses mv to create the JSON files so they change is atomic. If we wrote to the file directly instead, we could get occasional errors when reading it.
- We store the modification time before we read the value. There's a race condition: the value may change after we retrieved the modification time, but before we read the value. But it doesn't break the code: we return the correct value, but we might read it from the file once more next time.
- I guess the cron process doesn't change all the files all the time, so the real benefit of this kind of cache might be much lesser in your real environment.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.