Re: Issue perf attaching to processes creating many short-live threads
David Ahern <[email protected]>
| Newsgroups | gmane.linux.oprofile |
|---|---|
| Message-ID | <562A8C0F.4090607__11390.6298568056$1445629349$gmane$org@gmail.com> |
On 10/23/15 1:27 PM, William Cohen wrote: > On 10/23/2015 02:56 PM, David Ahern wrote: >> On 10/23/15 12:52 PM, William Cohen wrote: >>> Earlier this month Rei Odeira found that the oprofile tool operf would >>> have problems attaching and monitoring a process that created many >>> very short-lived threads. It looks like the kernel's perf tool also >>> has issues when attempting to attach and monitor a process that is >>> creating many short-lived threads. >> >> known a problem. If this is the problem I think it is you will find that strace shows perf stuck walking /proc directory. >> >> David >> > > Hi David, > > Is the following thread related to the problem? > > [PATCH 1/1] perf,tools: add time out to force stop endless mmap processing" > http://lkml.iu.edu/hypermail/linux/kernel/1506.1/02251.html > > Or is there some other thread about the problem? That's a different problem as I recall -- a single process constantly changing mmaps such that perf never has a chance to read the file. I was referring to something like 'make -j 1024' on a large system (e.g., 512 or 1024 cpus) and then starting perf. This is the same problem you are describing -- lot of short lived processes. I am fairly certain I described the problem on lkml or perf mailing list. Not even the task_diag proposal (task_diag uses netlink to push task data to perf versus walking /proc) has a chance to keep up. David ------------------------------------------------------------------------------