luke
/
verilator
mirror of https://github.com/verilator/verilator.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
verilator/test_regress/t/t_gantt_io.out

48 lines
1.4 KiB
Plaintext
Raw Normal View History

Tests: Add t_gantt_io test
2021-09-04 18:44:13 +02:00
Verilator Gantt report
Argument settings:
Improve run-time profiling The --prof-threads option has been split into two independent options: 1. --prof-exec, for collecting verilator_gantt and other execution related profiling data, and 2. --prof-pgo, for collecting data needed for PGO The implementation of execution profiling is extricated from VlThreadPool and is now a separate class VlExecutionProfiler. This means --prof-exec can now be used for single-threaded models (though it does not measure a lot of things just yet). For consistency VerilatedProfiler is renamed VlPgoProfiler. Both VlExecutionProfiler and VlPgoProfiler are in verilated_profiler.{h/cpp}, but can be used completely independently. Also re-worked the execution profile format so it now only emits events without holding onto any temporaries. This is in preparation for some future optimizations that would be hindered by the introduction of function locals via AstText. Also removed the Barrier event. Clearing the profile buffers is not notably more expensive as the profiling records are trivially destructible.
2022-03-25 20:46:50 +01:00
+verilator+prof+exec+start+2
+verilator+prof+exec+window+2
Tests: Add t_gantt_io test
2021-09-04 18:44:13 +02:00
Improve --prof-exec infrastructure and report Again --prof-exec have bit-rotted a little with all the recent changes to the structure of the generated code. This patch contains a few improvements: - Repalce the eval/evl_loop begin/end events with generic section_push/section_pop events, that can be arbitrarily sprinkled into the generate code (so long as they are matched correctly) to measure various sections. The report then contains a nested profile of the sections, and the VCD trace shows the section names. - Better handling of exec graphs - Clearer overall statistics
2023-05-10 13:12:34 +02:00
Summary:
Total elapsed time = 23415 rdtsc ticks
Parallelized code = 82.51% of elapsed time
Total threads = 2
Total CPUs used = 2
Total mtasks = 7
Total yields = 0
Parallelized code, measured:
Thread utilization = 14.22%
Speedup = 0.284x
Parallelized code, predicted during static scheduling:
Thread utilization = 63.22%
Speedup = 1.26x
All code, measured:
Thread utilization = 20.48%
Speedup = 0.41x
All code, measured, scaled by predicted speedup:
Thread utilization = 56.80%
Speedup = 1.14x
Tests: Add t_gantt_io test
2021-09-04 18:44:13 +02:00
Improve run-time profiling The --prof-threads option has been split into two independent options: 1. --prof-exec, for collecting verilator_gantt and other execution related profiling data, and 2. --prof-pgo, for collecting data needed for PGO The implementation of execution profiling is extricated from VlThreadPool and is now a separate class VlExecutionProfiler. This means --prof-exec can now be used for single-threaded models (though it does not measure a lot of things just yet). For consistency VerilatedProfiler is renamed VlPgoProfiler. Both VlExecutionProfiler and VlPgoProfiler are in verilated_profiler.{h/cpp}, but can be used completely independently. Also re-worked the execution profile format so it now only emits events without holding onto any temporaries. This is in preparation for some future optimizations that would be hindered by the introduction of function locals via AstText. Also removed the Barrier event. Clearing the profile buffers is not notably more expensive as the profiling records are trivially destructible.
2022-03-25 20:46:50 +01:00
MTask statistics:
Improve --prof-exec infrastructure and report Again --prof-exec have bit-rotted a little with all the recent changes to the structure of the generated code. This patch contains a few improvements: - Repalce the eval/evl_loop begin/end events with generic section_push/section_pop events, that can be arbitrarily sprinkled into the generate code (so long as they are matched correctly) to measure various sections. The report then contains a nested profile of the sections, and the VCD trace shows the section names. - Better handling of exec graphs - Clearer overall statistics
2023-05-10 13:12:34 +02:00
Longest mtask id = 5
Longest mtask time = 6.16% of time elapsed in parallelized code
Verilator_gantt now shows the predicted mtask times, eval times, and additional statistics.
2021-09-24 04:59:36 +02:00
min log(p2e) = -3.681 from mtask 5 (predict 30, elapsed 1190)
max log(p2e) = -2.409 from mtask 8 (predict 107, elapsed 1190)
mean = -2.992
stddev = 0.459
e ^ stddev = 1.583
Tests: Add t_gantt_io test
2021-09-04 18:44:13 +02:00
Improve --prof-exec infrastructure and report Again --prof-exec have bit-rotted a little with all the recent changes to the structure of the generated code. This patch contains a few improvements: - Repalce the eval/evl_loop begin/end events with generic section_push/section_pop events, that can be arbitrarily sprinkled into the generate code (so long as they are matched correctly) to measure various sections. The report then contains a nested profile of the sections, and the VCD trace shows the section names. - Better handling of exec graphs - Clearer overall statistics
2023-05-10 13:12:34 +02:00
CPU info:
Id | Time spent executing MTask | Socket | Core | Model
| % of elapsed ticks / ticks | | |
====|============================|========|======|======
10 | 20.18% / 4725 | 0 | 10 | Test Ryzen 9 3950X 16-Core Processor
19 | 3.29% / 770 | 0 | 3 | Test Ryzen 9 3950X 16-Core Processor
Tests: Add t_gantt_io test
2021-09-04 18:44:13 +02:00
Improve run-time profiling The --prof-threads option has been split into two independent options: 1. --prof-exec, for collecting verilator_gantt and other execution related profiling data, and 2. --prof-pgo, for collecting data needed for PGO The implementation of execution profiling is extricated from VlThreadPool and is now a separate class VlExecutionProfiler. This means --prof-exec can now be used for single-threaded models (though it does not measure a lot of things just yet). For consistency VerilatedProfiler is renamed VlPgoProfiler. Both VlExecutionProfiler and VlPgoProfiler are in verilated_profiler.{h/cpp}, but can be used completely independently. Also re-worked the execution profile format so it now only emits events without holding onto any temporaries. This is in preparation for some future optimizations that would be hindered by the introduction of function locals via AstText. Also removed the Barrier event. Clearing the profile buffers is not notably more expensive as the profiling records are trivially destructible.
2022-03-25 20:46:50 +01:00
Writing profile_exec.vcd