On Sep 24, 2014 2:34 AM, James wirel...@tampabay.rr.com wrote:
Hello
PyTimeChart is another wonderful tool that complements
Ftrace/trace-cmd/KernelShark. [1] The systemd supporters would be keenly
wise if they added pytimechart to Gentoo, so those (systemd) reticent to
change, can actually see just how wonderful systemd is Here in
slide (26) we see intel extolling systemd. If Intel thinks systemd
is wonderful, then it must be wonderful. (?) [2] as shown in the paper
Elcell_tardy.pdf.
PyTimeChart is also wonderful in that it provides a graphical way to
spot problems quickly. Most major (linux) distros have both PyTimeChart
and Ftrace/trace-cmd/KernelShark. Together folks use PyTimeChart to
monitor and identify low-level or low-level-application-interaction
problems, and then use Ftrace/trace-cmd/KernelShark for fine grain
filtering, collection and analysis of those
low-level-application-interaction
issues.
Im just going to go out on a limb here, but is it possible that you dont
understand what either systemd or pytimechart do?
both your description of pytimechart and the rejection of intel's claim...
seem to point to a lack of understanding.
Intel isnt saying systemd is amazing only that it doesnt operate by
spawning many short-lived processes in the same way as upstart or sysvinit
(which start shell scripts which start programs). systemd starts the
services directly based on the contents of the units.
pytimechart cannot be used to monitor events - its just a visualizer for
existing trace mechanisms.
I have not opened a bug requesting PyTimeChart.
perhaps you should.
hth,
James
[1] https://pythonhosted.org/pytimechart/index.html
[2] elinux.org/images/6/63/Elce11_tardy.pdf
