James Wu f037803290 Add ChromiumEventLogger, log FXGraphCache and AOTAutogradCache (#132864) ... This PR implements ChromiumEventLogger in all @dynamo_timed events. For each dynamo timed call, we log: - A start event before starting the function execution - An end event after finishing the function execution - An extra pair of start/end events for any phase names included in dynamo. Separately, this also gives us the ability to log instant events. I use them to log cache hits/misses as a first step. The little arrows on the bottom of the UI are cache hits/misses, and you can look at cache details by clicking each triangle. The outputted chromium trace events can be viewed in perfetto for a timeline of an execution. Here's what it looks like for a run of nanogpt:  And another with warm start:  Trace events are based around the JSON Event format: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview We may want to switch to the less deprecated Protobuf format later, but so far I don't see any features we care about supported there. Internal FB employees can see a link to this in the tlparse output: https://interncache-all.fbcdn.net/manifold/tlparse_reports/tree/logs/.tmpVi1FIl/dedicated_log_torch_trace_bb4zl_bc.log/index.html I'll also work on logging these Pull Request resolved: https://github.com/pytorch/pytorch/pull/132864 Approved by: https://github.com/aorenste		2024-08-10 01:15:53 +00:00
..
__init__.py	[BE][Easy][14/19] enforce style for empty lines in import segments in torch/_[a-c]*/ and torch/_[e-h]*/ and torch/_[j-z]*/ (#129765)	2024-07-31 10:42:50 +00:00
_internal.py	Add ChromiumEventLogger, log FXGraphCache and AOTAutogradCache (#132864)	2024-08-10 01:15:53 +00:00
_registrations.py	[BC breaking] move benchmarking + prefer inductor path (#132827)	2024-08-08 00:47:45 +00:00
structured.py	Dump files that look like FX graphs to structured log (#132100)	2024-07-31 18:45:28 +00:00