Dear Maintainer,

I changed the configuration to add an FPing probe flavor with pings=2000
(and step=2100) specified, and a few targets using that probe.

The motication for this is that my ISP considers the number of packets
lost within a 2000-ping sample to be a canonical metric for reliability.
So I would like to collect statistics using this metric in order to have
have data for any complaints in the future.

The backend smokeping process seems to work just fine. The data is being
collected, and the 3 and 30 hour graphs are rendered in reasonable time
(~2s).

However when I go to the 10 day (or longer) graph URL for such target,
the CGI script hogs CPU and eats all available RAM (8GB) until it is
terminated by the OOM-killer after four minutes or so, resulting in a
503 or 504 response from Apache. The longest period I was able to graph
successfully was about 4 days.

Note that the above is with about 18 hours worth of data. The RRD files
for targets with default configuration are about 2.9MB, and the ones for
2000 pings are 248MB.