https://bugzilla.redhat.com/show_bug.cgi?id=1376861
Bug ID: 1376861
Summary: pcp pmwebd performance improvements
Product: Fedora
Version: rawhide
Component: pcp
Assignee: nathans@xxxxxxxxxx
Reporter: fche@xxxxxxxxxx
QA Contact: extras-qa@xxxxxxxxxxxxxxxxx
CC: brolley@xxxxxxxxxx, fche@xxxxxxxxxx, lberk@xxxxxxxxxx,
mgoodwin@xxxxxxxxxx, nathans@xxxxxxxxxx,
pcp@xxxxxxxxxxx, scox@xxxxxxxxxx
pmwebd is slow to answer certain types of queries, sometimes painfully so.
Some ideas:
- fix multithreading problems in libpcp, so that the core pmwebapi portion of
pmwebd could become multithreaded
- fix multithreading problems in libpcp, so that the graphite pmwebapi portion
can be fully multithreaded too (with concurrent service of different requests,
rather than just concurrent scans of multiple archives for a given request)
- for graphite mode, cache archive metadata somehow. We can't keep all of the
archives open because of FD limits. Plus we must be tolerant to archives that
are being actively written-to (so the metadata cache must be flushable).
- for graphite-json query outputs, investigate whether all the JSON "{null,
$timestamp}" entries actually must be emitted. Maybe the graphite/grafana
webapps we bundle can fill in that stuff.
- for graphite-png query outputs, rework the representation of all the
timeseries in memory as a big rectangular vector-of-vectors. The nulls/nans
probably don't need to be materialized, and costing perhaps tens or hundreds of
MB (for massive sets of series).
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=bRgH2IIzfe&a=cc_unsubscribe
|