2,257
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: − == <code>parse_smaps</code> ==+ − + + + Line 27:
Line 29: + + + +
no edit summary
== Dump ==
== Dump ==
Surprisingly, but the mem-drain time is not the biggest. It's "only" ~0.02 seconds. There are places in code that take longer.
Time spent in this routine is about 0.1 seconds on dump. This one exploits /proc heavily. For a container with 11 tasks the syscall stats look like
=== <code>parse_smaps</code> ===
Time spent in this routine is up to 0.2 seconds on dump. This one exploits /proc heavily. For a container with 11 tasks the syscall stats look like
834 read
834 read
1438 openat(4, "map-symlink", O_RDONLY) = 5
1438 openat(4, "map-symlink", O_RDONLY) = 5
11 openat(AT_FDCWD, "/proc/$pid/map_files", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
11 openat(AT_FDCWD, "/proc/$pid/map_files", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
=== <code>parasite_fuxup_vdso</code> ===
The 2nd longest routine. It takes ~ 0.07 seconds on dump.
== Restore ==
== Restore ==