This is an archive of the discontinued LLVM Phabricator instance.

Differential D44005

[LNT] Document how to import Performance profiles in JSON format.
ClosedPublic

Authored by marxin on Mar 2 2018, 5:49 AM.

Details

Reviewers
cmatthews
MatzeB
jgreenhalgh
Commits
rL327112: Document how to import Performance profiles in JSON format.
Summary

Switch documentation to use JSON format version 2. It fixes:
https://bugs.llvm.org/show_bug.cgi?id=35297.

Diff Detail

Repository
rL LLVM

Event Timeline

marxin created this revision.Mar 2 2018, 5:49 AM
cmatthews accepted this revision.Mar 5 2018, 4:58 PM
This revision is now accepted and ready to land.Mar 5 2018, 4:58 PM
marxin added a comment.Mar 6 2018, 4:23 AM

I've just requested SVN commit access.
Can you please commit the in behalf of me?

Closed by commit rL327112: Document how to import Performance profiles in JSON format. (authored by marxin). · Explain WhyMar 9 2018, 3:04 AM
This revision was automatically updated to reflect the committed changes.
Herald added a subscriber: llvm-commits. · View Herald TranscriptMar 9 2018, 3:04 AM

Revision Contents

PathSize
lnt/
trunk/
docs/
36 lines

Diff 137713

lnt/trunk/docs/profiles.rst

Show First 20 Lines • Show All 47 Lines • ▼ Show 20 Lines
``/tmp/my_profile.lntprof`` is now an LNT profile in a space-efficient binary form. To prepare it to be sent via JSON, we must base-64 encode it:: ``/tmp/my_profile.lntprof`` is now an LNT profile in a space-efficient binary form. To prepare it to be sent via JSON, we must base-64 encode it::
base64 -i /tmp/my_profile.lntprof > /tmp/my_profile.txt base64 -i /tmp/my_profile.lntprof > /tmp/my_profile.txt
Now we just need to add it to the report. Profiles look similar to hashes in that they are samples with string data:: Now we just need to add it to the report. Profiles look similar to hashes in that they are samples with string data::
{ {
"Machine": { "format_version": "2",
"machine": {
... ...
}, },
"Run": { "run": {
... ...
}, },
"Tests": [ "tests": [
{ {
"Data": [ "name": "nts.suite1/program1",
0.1056, "execution_time": [ 0.1056, 0.1055 ],
0.1055 "profile": "eJxNj8EOgjAMhu99Cm9wULMOEHgBE888QdkASWCQFWJ8e1v04JIt+9f//7qmfkVoEj8yMXdzO70v/RJn2hJYrRQiveSWATdJvwe3jUtgecgh9Wsh9T6gyJvKUjm0kegK0mmt9UCjJUSgB5q8KsobUJOQ96dozr8tAbRApPbssOeCcm83ddoLC7ijMcA/RGUUwXt7iviPEDLJN92yh62LR7I8aBUMysgLnaKNFNzzMo8y7uGplQ4sa/j6rfn60WYaGdRhtT9fP5+JUW4="
],
"Info": {},
"Name": "nts.suite1/program1.exec"
},
{
"Data": [
"eJxNj8EOgjAMhu99Cm9wULMOEHgBE888QdkASWCQFWJ8e1v04JIt+9f//7qmfkVoEj8yMXdzO70v/RJn2hJYrRQiveSWATdJvwe3jUtgecgh9Wsh9T6gyJvKUjm0kegK0mmt9UCjJUSgB5q8KsobUJOQ96dozr8tAbRApPbssOeCcm83ddoLC7ijMcA/RGUUwXt7iviPEDLJN92yh62LR7I8aBUMysgLnaKNFNzzMo8y7uGplQ4sa/j6rfn60WYaGdRhtT9fP5+JUW4="
],
"Info": {},
"Name": "nts.suite2/program1.profile"
} }
] ]
} }
Supported formats Supported formats
----------------- -----------------
Linux Perf Linux Perf
~~~~~~~~~~ ~~~~~~~~~~
Perf profiles are read directly from the binary ``perf.data`` file without using the ``perf`` wrapper tool or any Linux/GPL headers. This makes it runnable on non-Linux platforms although this is only really useful for debugging as the profiled binary / libraries are expected to be readable. Perf profiles are read directly from the binary ``perf.data`` file without using the ``perf`` wrapper tool or any Linux/GPL headers. This makes it runnable on non-Linux platforms although this is only really useful for debugging as the profiled binary / libraries are expected to be readable.
▲ Show 20 Lines • Show All 41 Lines • Show Last 20 Lines