Difference between revisions of "Performance research"
Jump to navigation
Jump to search
(Created page with "Written here are performance issues found == <code>parse_smaps</code> == This guy exploits /proc heavily. For a container with 11 tasks the syscall stats look like 834 ...") |
|||
| Line 1: | Line 1: | ||
Written here are performance issues found | Written here are performance issues found | ||
| + | |||
| + | == Dump == | ||
== <code>parse_smaps</code> == | == <code>parse_smaps</code> == | ||
| Line 18: | Line 20: | ||
Time spent in this routine is about 0.1 seconds on dump. | Time spent in this routine is about 0.1 seconds on dump. | ||
| + | |||
| + | == Restore == | ||
Revision as of 20:52, 30 January 2014
Written here are performance issues found
Dump
parse_smaps
This guy exploits /proc heavily. For a container with 11 tasks the syscall stats look like
834 read 1451 fstat 1462 close 1642 openat
while opens and stats happen on
193 openat(4, "map-symlink", O_RDONLY) = -1 ENOENT (No such file or directory)
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
Time spent in this routine is about 0.1 seconds on dump.