Skip to content

Conversation

@kolyshkin
Copy link
Contributor

For some reason, commit 69cf037 (PR #18697) chose not to use information
already fetched, and called cgroups.FindCgroupMountpoint() instead.

This is not a cheap call, as it has to parse the whole nine yards
of /proc/self/mountinfo, and the info which it tries to get (whether
the pids controller is present) is already available from cgMounts map.

kolyshkin added 2 commits May 22, 2020 13:13
For some reason, commit 69cf037 chose not to use information
already fetched, and called cgroups.FindCgroupMountpoint() instead.
This is not a cheap call, as it has to parse the whole nine yards
of /proc/self/mountinfo, and the info which it tries to get (whether
the pids controller is present) is already available from cgMounts map.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Some were misleading or vague, some were plain wrong.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@kolyshkin
Copy link
Contributor Author

CI failures appear to be caused by github issues

#45 254.5 Cloning into '/tmp/tmp.8MxCqWQ8md/src/github.com/subosito/gotenv'...
[2020-05-22T20:21:37.422Z] #45 254.5 error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Timeout

@kolyshkin
Copy link
Contributor Author

@thaJeztah PTAL

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@thaJeztah thaJeztah merged commit 55f0acd into moby:master May 25, 2020
@thaJeztah thaJeztah added kind/refactor PR's that refactor, or clean-up code status/2-code-review labels May 25, 2020
@thaJeztah thaJeztah added this to the 20.03.0 milestone May 25, 2020
@thaJeztah
Copy link
Member

@kolyshkin do you know how much time we save with this? Wondering if we should backport this (given that the fix itself is tiny and trivial), or not worth the effort?

@kolyshkin
Copy link
Contributor Author

@kolyshkin do you know how much time we save with this? Wondering if we should backport this (given that the fix itself is tiny and trivial), or not worth the effort?

Up to 0.01s in busy scenarios, much less so on a relatively idle system. If it's a straightforward backport, I'd do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/refactor PR's that refactor, or clean-up code status/2-code-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants