summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2025-03-04 12:55:54 +0100
committerKlaus Aehlig <klaus.aehlig@huawei.com>2025-03-10 16:28:59 +0100
commitd8ae602433f61f61f6e8e9d08052323e45a6152e (patch)
tree5a900490a52ef8eb535c136cf9fdc5e9c371b32b /doc
parent42453a89d18d9cad169172e2803fca9609abf34d (diff)
downloadjustbuild-d8ae602433f61f61f6e8e9d08052323e45a6152e.tar.gz
profiling design: drop asynchronous writing
... as it turns out that the synchronous writing is fast enough and hence we can avoid all the problems of background processes.
Diffstat (limited to 'doc')
-rw-r--r--doc/future-designs/profiling.md11
1 files changed, 0 insertions, 11 deletions
diff --git a/doc/future-designs/profiling.md b/doc/future-designs/profiling.md
index 55f5fa5a..d09b5bd4 100644
--- a/doc/future-designs/profiling.md
+++ b/doc/future-designs/profiling.md
@@ -135,17 +135,6 @@ the following key (and more keys possibly added in the future).
completing the action can be taken; in this case, the fact
that this fallback was taken is also recorded.
-Additionally, `just` will receive a flag `--async-profile`,
-defaulting to false. If given, the writing of the action graphs (if
-`--dump-graph` or `--dump-plain-graph` is given) as well the profile (if
-`--profile` is given) are asynchronously written in a forked-off
-subprocess (note that, at the moments those files are written,
-`just` is single threaded) and the main process does not wait for
-the child (i.e., follows a fork-and-forget strategy); in this case,
-profiling is done only on a best-effort basis. Using asynchronous
-profile logging, the regular developer workflow is not affected by
-the overhead of writing these detailed machine-readable logs.
-
### `just` options `--dump-graph` and `--dump-plain-graph` become cummulative
The options `--dump-graph` and `--dump-plain-graph` change their