| commit | 10298945e5abe99ff8348abb309becd6c5364681 | |
| author | James Wu <jjwu@fb.com> | |
| Tue, 15 May 2018 23:55:47 +0000 (15 16:55 -0700) | ||
| committer | Hhvm Bot <hhvm-bot@users.noreply.github.com> | |
| Wed, 16 May 2018 00:02:15 +0000 (15 17:02 -0700) | ||
| tree | f4718cd8da7f0cdb0f293728593e7e215cb469d0 | treesnapshot (tar.gz zip) |
| parent | b2abcac3535fc3ef367c5935c43475ac9cb6a48a | commitdiff |
Updates to profiling
Summary:
So the runner I introduced in the last diff is good for getting a general idea for memory and time usage, but it's not as good for profiling: we start up and shut down hh_single_parse/hh_parse every single time, which means the majority of our profiling data is just this initialization.
This diff adds hh_single_parse --benchmark_batch, which allows you to benchmark running a list of files with the ffp. This initializes shared memory once, and then runs every file x times, where x is an argument passed in.
Reviewed By: arxanas
Differential Revision: D7999232
fbshipit-source-id: a89de9229a722efbd62ad9dcd6bf7896c89a0663
Summary:
So the runner I introduced in the last diff is good for getting a general idea for memory and time usage, but it's not as good for profiling: we start up and shut down hh_single_parse/hh_parse every single time, which means the majority of our profiling data is just this initialization.
This diff adds hh_single_parse --benchmark_batch, which allows you to benchmark running a list of files with the ffp. This initializes shared memory once, and then runs every file x times, where x is an argument passed in.
Reviewed By: arxanas
Differential Revision: D7999232
fbshipit-source-id: a89de9229a722efbd62ad9dcd6bf7896c89a0663
| hphp/hack/src/hh_single_parse.ml | diffblobblamehistory |