Replace .pftrace in docs with .perfetto-trace.

Recently we fielded some feedback from someone wondering what to do with
a .pftrace file, so updating this documentation to use .perfetto-trace
which is (hopefully!) a clearer filename (and is what we use elsewhere).

Test: Not sure how to test this change; let me know!

Change-Id: I4f491da2c44132aa70abac2d56c4748674281e1f
6 files changed
tree: 3c6d28e3e42f7567bfe1a2bb1e5a0a06e617fc1c
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. src/
  13. test/
  14. tools/
  15. ui/
  16. .clang-format
  17. .clang-tidy
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .style.yapf
  22. Android.bp
  23. Android.bp.extras
  24. BUILD
  25. BUILD.extras
  26. BUILD.gn
  27. CHANGELOG
  28. codereview.settings
  29. DIR_METADATA
  30. heapprofd.rc
  31. LICENSE
  32. METADATA
  33. MODULE_LICENSE_APACHE2
  34. OWNERS
  35. perfetto.rc
  36. PerfettoIntegrationTests.xml
  37. PRESUBMIT.py
  38. README.chromium
  39. README.md
  40. TEST_MAPPING
  41. traced_perf.rc
  42. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.