28
top 4 comments
sorted by: hot top controversial new old
[-] o11c@programming.dev 5 points 1 year ago* (last edited 1 year ago)

It's worth noting that the http.server module is based on socketserver.BaseServer.serve_forever, which is a atrocious.

It uses a busy loop with a delay, so it both burns CPU and is unresponsive.

(The fact that Python has had broken signal handling since 3.5 also hurts - EINTR should never be ignored from blocking calls)

[-] jim@programming.dev 2 points 1 year ago

I was just about to uninstall nginx...

On a serious note: I'm not sure of the details of socketserver but I would think opening a socket would not be a cpu intensive process.

[-] o11c@programming.dev 0 points 1 year ago

The comments in the code explain exactly what the problem is and how to fix it, and it would take less than 30 minutes to implement and test that (assuming you don't just grab someone else's version - there's a reason I know the time), but nobody has committed it in ... at least 13 years since the comment was written; I'm not digging any further through imported SVN history.

[-] tenth@lemmy.world 3 points 1 year ago

Thats neat. Thanks for sharing

load more comments
view more: next ›
this post was submitted on 29 Jun 2023
28 points (93.8% liked)

Python

6187 readers
3 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

October 2023

November 2023

PastJuly 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS