High CPU usage in irc.server.

Open
#193 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start by locating the irc.server select() loop and inspect why sockets remain ready_to_read across iterations. Reproduce the behavior with an active connection and verify that the loop no longer spins continuously or causes high CPU usage; add a regression test if the existing test structure covers this path.

Written by the indexing model from the issue text.

Description

help wanted

The select() call returns immediately almost always, since the sockets are usually ready_to_read. This effectively creates a tight loop and very high CPU usage for any active connection.

Dominant language
Python
Stars
422
Forks
91
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/irc

All issues in jaraco/irc

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.