Mercurial > hg
diff contrib/chg/chg.c @ 47024:8fcc0a829f3d
chg: pass --no-profile to disable profiling when starting hg serve
If profiling is enabled via global/user config (as far as I can tell, this
doesn't affect use of the --profile flag, but it probably does affect --config
profiling.enabled=1), then the profiling data can be *cumulative* for the
lifetime of the chg process.
This leads to some "interesting" results where hg claims the walltime is
something like 200s on a command that took only a second or two to run. Worse,
however, is that with at least some profilers (such as the default "stat"
profiler), this can cause a large slowdown while generating the profiler output.
Differential Revision: https://phab.mercurial-scm.org/D10470
author | Kyle Lippincott <spectral@google.com> |
---|---|
date | Fri, 16 Apr 2021 16:21:26 -0700 |
parents | 0c320e6032f1 |
children | cf4d2f31660d |
line wrap: on
line diff
--- a/contrib/chg/chg.c Fri Apr 16 15:31:05 2021 -0700 +++ b/contrib/chg/chg.c Fri Apr 16 16:21:26 2021 -0700 @@ -240,13 +240,8 @@ const char *hgcmd = gethgcmd(); const char *baseargv[] = { - hgcmd, - "serve", - "--cmdserver", - "chgunix", - "--address", - opts->initsockname, - "--daemon-postexec", + hgcmd, "serve", "--no-profile", "--cmdserver", + "chgunix", "--address", opts->initsockname, "--daemon-postexec", "chdir:/", }; size_t baseargvsize = sizeof(baseargv) / sizeof(baseargv[0]);