Closed adamf663 closed 3 years ago
some details: built on centos7. a strangeness is that wrk2 will run perfectly for anywhere between 5 minuts and an hour; then the process will go to 100% cpu (or half if there's another runaway wrk2), and I/O slows to a crawl at about 10% the previous level.
FYI: pull request #33 Re-connect when peer closes the connection, fixes it. It really ought to get merged some day.
That might also be about: https://github.com/giltene/wrk2/issues/106
Has anyone else experienced wrk2's cpu usage shooting up to 100% after running for a while?