-
Notifications
You must be signed in to change notification settings - Fork 34
Labels
bugSomething isn't workingSomething isn't workingruntimeWork in the C++ runtime portion of the codeWork in the C++ runtime portion of the code
Description
I am noticing that CPU usage is maxing out a single core when no work is actually being performed. I noticed this for task.wait, process.run, and net.serve. They all use the uv library, so maybe that's a hint towards the underlying issue?
Example 1: task wait
local task = require("@lute/task")
task.wait(100000)Example 2: sleep
local process = require("@std/process")
process.run({ "sleep", "100000" })Example 3: net serve
local net = require("@lute/net")
net.serve({ port = 8080, handler = function() return "ok" end })Running any of these examples results in a single core being pinged to around 100%.
Windows x86-64 (16 logic cores, so 6.25% represents one full core):

I have not tested this on macos.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingruntimeWork in the C++ runtime portion of the codeWork in the C++ runtime portion of the code
