Show More
@@ -34,6 +34,21 b' extension will be used by default unless' | |||||
34 | One day we may use this environment variable to switch to new experimental |
|
34 | One day we may use this environment variable to switch to new experimental | |
35 | binding crates like a hypothetical ``HGWITHRUSTEXT=hpy``. |
|
35 | binding crates like a hypothetical ``HGWITHRUSTEXT=hpy``. | |
36 |
|
36 | |||
|
37 | Profiling | |||
|
38 | ========= | |||
|
39 | ||||
|
40 | Setting the environment variable ``RUST_LOG=trace`` will make hg print | |||
|
41 | a few high level rust-related performance numbers. It can also | |||
|
42 | indicate why the rust code cannot be used (say, using lookarounds in | |||
|
43 | hgignore). | |||
|
44 | ||||
|
45 | ``py-spy`` (https://github.com/benfred/py-spy) can be used to | |||
|
46 | construct a single profile with rust functions and python functions | |||
|
47 | (as opposed to ``hg --profile``, which attributes time spent in rust | |||
|
48 | to some unlucky python code running shortly after the rust code, and | |||
|
49 | as opposed to tools for native code like ``perf``, which attribute | |||
|
50 | time to the python interpreter instead of python functions). | |||
|
51 | ||||
37 | Developing Rust |
|
52 | Developing Rust | |
38 | =============== |
|
53 | =============== | |
39 |
|
54 |
General Comments 0
You need to be logged in to leave comments.
Login now