niczero

From https://github.com/blog/542-introducing-resque

We are constantly overloaded and rely very, very heavily on our queue. If it’s
backed up, we need to know why. We need to know if we can fix it. We need
workers to not get stuck and we need to know when they are stuck.

We need to see what the queue is doing. We need to see what jobs have failed.
We need stats: how long are workers living, how many jobs are they processing,
how many jobs have been processed total, how many errors have there been, are
errors being repeated, did a deploy introduce a new one?

niczero

perl -M... -E'say $_, q{ : }, ${main::}{$_} for keys %{main::}'

niczero

perl -MMojar::Mysql::Connector=cnfdir,data,cnf,tester_localhost,-dbh,1
    -E'say join q{, }, main->dbh->selectrow_array(q{SELECT 1,2,3})'

niczero

# Mnm

## Cache locally

Want to buffer all stats locally on the source (ie client) box.  This could be via rrdtools or collectd or bespoke files (eg series of tsv).  Collectd would be an obvious choice if this resource was shared, but want to continue collecting even when net is down.  Undecided whether to collect all stats in one global 'file' or have one 'file' per stat.  It would be nice if this was a priority queue but that's probably an overcomplication at this stage.

## Connect minimally

Would rather have a single connection to the db and pipe a sequence of queries through that.  Perhaps this runs from a daemon and so the connection only closes when (a) the server kicks it off, (b) the server is completely twisted, or (c) the daemon restarts (or all three).

niczero

Comparative Installations

Installation on core perl 5.18.2 via

cpanm -l /tmp/test Package

with all sources cached in .cpanm (to eliminate download times). Parallel times are done using

HARNESS_OPTIONS=j9

niczero

Summary

Template reuse is awesome, either via extending templates or via layouts. But what about together? A tiny change to rendering allows them to be combined, which makes it even easier to design, manage, and maximise reuse of templates.

Use Case 1: Default layout

The Rendering Guide clearly shows the value of setting a default layout and also the value of template inheritance (using 'extends'), but currently these can't be used together: the default layout is ignored and therefore missing from the rendered output.

Use Case 2: Dynamic layout

niczero

perl -MMojo::Base=strict -MEncode -E'say qq{$_: }. encode($_, q{Ue: }. chr(220) .q{; Euro: }. chr(8364)) for qw(utf-8 latin1 iso-8859-15 utf-16)'

niczero

open my $handle, '<:encoding(UTF-8)', $file;
open my $handle, '<:encoding(iso-8859-1)', $file;

open my $handle, '<', $file;
binmode $handle, ':encoding(UTF-8)';

use open ':encoding(UTF-8)';
use open ':encoding(iso-8859-1)';
use open ':locale';

niczero

Client-side Markdown

https://github.com/tanakahisateru/js-markdown-extra
Promising in terms of functionality, but still very buggy and currently has a slow rate of development.

https://leeoniya.github.io/reMarked.js/
Definitely worth considering. (Also: nice page of links.)

https://github.com/jmcmanus/pagedown-extra
Has a good list of desirable functionality, but far too heavyweight, as proved by the time it takes to render its homepage.

niczero

use Mojo::Base -strict;

use Test::More;
use Test::Mojo;

use FindBin; 
require "$FindBin::Bin/../x";

my $t = Test::Mojo->new;