OpenStack cross service/project profiler
Go to file
Tovin Seven 768d8eac2a Change some bindings to one-time bindings
Almost our data-binding in this template is two-way binding.
It is not necessary, 2-way binding will add lots of watchers,
so, our html page will very slow with large trace.

I tried with some html outputs >20MB, it's terrible.

Reference (in One-time binding section):
https://docs.angularjs.org/guide/expression

Change-Id: Ida2f567abff356f20ddcc1d8535a22fd906035ea
2017-02-07 08:54:33 +00:00
devstack Fix enabling order specify in README.rst 2017-01-17 10:13:57 -06:00
doc Add a redis driver 2016-11-07 06:35:52 -06:00
osprofiler Change some bindings to one-time bindings 2017-02-07 08:54:33 +00:00
releasenotes Add reno for release notes management 2016-11-03 18:38:01 +08:00
tools Trivial: Remove vim header from source files 2016-09-24 05:25:17 +08:00
.gitignore Add reno for release notes management 2016-11-03 18:38:01 +08:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:34:15 +00:00
.testr.conf Add functional test for notifier backend 2016-12-15 19:36:35 +05:30
CONTRIBUTING.rst Add CONTRIBUTING.rst 2016-02-29 13:42:14 +08:00
LICENSE Init Strucutre of lib 2014-01-09 11:25:23 +04:00
README.rst Show team and repo badges on README 2016-11-25 13:13:03 +01:00
requirements.txt Merge "Replace logging with oslo_log" 2016-11-11 17:30:09 +00:00
setup.cfg Add py35 tox virtualenv 2016-12-15 19:39:54 +05:30
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Merge "Add Log Insight driver" 2016-11-07 19:44:53 +00:00
tox.ini Merge "Add functional test for notifier backend" 2016-12-22 05:45:10 +00:00

README.rst

Team and repository tags

image

OSProfiler -- Library for cross-project profiling library

Latest Version

Downloads

OSProfiler provides a tiny but powerful library that is used by most (soon to be all) OpenStack projects and their python clients. It provides functionality to be able to generate 1 trace per request, that goes through all involved services. This trace can then be extracted and used to build a tree of calls which can be quite handy for a variety of reasons (for example in isolating cross-project performance issues).