From: Stuart Henderson <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] flent on openbsd loops, consuming available cpu/memory, after test completes (#221)
Date: Sun, 07 Mar 2021 07:24:40 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/221/792296152@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/221@github.com>
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
It spins for as long as I let it run or until it bumps into ulimit, RES grows at about 16M per 10 seconds.
There's not much difference in output with git head, apart from outputting Executing lines when gathering information at startup the only differences in output are that it doesn't print "[New thread 395121]" after "NetperfDemoRunner TCP download::4 finished" and timers expire in a different order, here's the diff
```
NetperfDemoRunner TCP download::1 finished
NetperfDemoRunner TCP download::3 finished
NetperfDemoRunner TCP download::4 finished
-[New thread 395121]
PingRunner Ping (ms) ICMP finished
Runner aggregation finished
TimerRunner Watchdog [Ping (ms) ICMP]: timer expired
TimerRunner Watchdog [Ping (ms) ICMP] finished
TimerRunner Watchdog [TCP download::2]: timer expired
TimerRunner Watchdog [TCP download::2] finished
-TimerRunner Watchdog [TCP download::1]: timer expired
-TimerRunner Watchdog [TCP download::4]: timer expired
-TimerRunner Watchdog [TCP download::1] finished
TimerRunner Watchdog [TCP download::3]: timer expired
-TimerRunner Watchdog [TCP download::4] finished
TimerRunner Watchdog [TCP download::3] finished
+TimerRunner Watchdog [TCP download::4]: timer expired
+TimerRunner Watchdog [TCP download::4] finished
+TimerRunner Watchdog [TCP download::1]: timer expired
+TimerRunner Watchdog [TCP download::1] finished
```
I'll add some prints in aggregators.py to try to figure out where it's spinning and get back to you.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/221#issuecomment-792296152
[-- Attachment #2: Type: text/html, Size: 2594 bytes --]
next prev parent reply other threads:[~2021-03-07 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 20:14 [Flent-users] " Stuart Henderson
2021-03-06 23:56 ` [Flent-users] " Toke Høiland-Jørgensen
2021-03-07 15:24 ` Stuart Henderson [this message]
2021-03-07 15:33 ` Stuart Henderson
2021-03-07 15:35 ` Stuart Henderson
2021-03-07 19:33 ` Stuart Henderson
2021-03-07 19:33 ` Stuart Henderson
2021-03-07 20:25 ` Toke Høiland-Jørgensen
2021-03-07 20:25 ` Toke Høiland-Jørgensen
2021-03-20 16:43 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issues/221/792296152@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP6GWZZBGNO74YEWST56KDITREVBNHHDCGJ4TM@reply.github.com \
--cc=subscribed@noreply.github.com \
--subject='[Flent-users] Re: [tohojo/flent] flent on openbsd loops, consuming available cpu/memory, after test completes (#221)' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox