But when the whole Python interpreter machinery has to run in the background, that will prevent your system from going to lower power states more often.
“It does not matter for this case” times 100 is how we get these power-hungry systems.
But when the whole Python interpreter machinery has to run in the background, that will prevent your system from going to lower power states more often.
“It does not matter for this case” times 100 is how we get these power-hungry systems.
I’m with the sibling commenter: Python’s heavy-weight-ness and overhead is a thing, yes, but it’s not the same kind of overhead that gets us to power hungry bloated systems—that stuff has more to do with (on the server) wakeups, memory thrashing from async GC, and careless addition of all sorts of background threads/services to applications without considering efficiency. On the desktop, bloat/overhead have more to do with questionable design choices made by UI frameworks, security/container layers that defeat some performance optimizations, and regular bloated browser-in-a-box GUI apps.
Python is a bad choice for high-throughput systems but not for reasons that make it power inefficient when used in a scripting capacity like tuned.
It's more likely someone using higher-level constructs for something that'll spend most of it's time doing NOTHING will write code that does less. Asyncio helps you write code that does nothing most of the time.
You think the Python interpreter just randomly executes stuff for shits and giggles? No but it does use more memory than something compiled to native.
Meanwhile: TLP is implemented in Bash.
Stop spreading FUD please it contributes negatively to the world.
What machinery?