Is it normal for

kobweb run

to lock up a whole thread(100% util) ?

Try running

./gradlew kobwebStart -t

instead and compare, same result? It's probably expected, especially the first time you run it. Compiling is hard, use all the CPU you can!

Yup, Webpack of course uses a lot when recompiling but dev server is always utilizing 100% of some thread even on IDLE

Ah, it's 100% utilized after everything started and the server is running? That's very strange

Yes

Thanks

I've got 150 hits on "FAILURE ..." and almost all of them are

"Selector didn't match" @/api

with same child element but it ends with

@ /{...}/

I can look into that, but 150 hits shouldn't cause 100% thread utiliziation

I'll try running it on a different project, let's see

Appreciate it

Okay will do

The last one (

examples/jb/counter

) is about as simple as a Kobweb project can get

trying with that one then

What's your OS?

Linux

I'll see if I can repro

yes

So maybe I should check my assumption. You're saying I'm locking a thread, but not necessarily locking up a CPU?

No not the whole CPU but always one of the threads when idling is at 100%, it changes to a different thread from time to time(~4,5 seconds)

suspend fun main: https://github.com/varabyte/kobweb/blob/a13d9696e813b483f4b00028a74f4d12555451ed/b[…]erver/src/main/kotlin/com/varabyte/kobweb/server/Application.kt while loop: https://github.com/varabyte/kobweb/blob/a13d9696e813b483f4b00028a74f4d12555451ed/b[…]erver/src/main/kotlin/com/varabyte/kobweb/server/Application.kt

Thread changing is probably by the OS scheduler but idk

Maybe the way I wrote that code is not thread friendly

yup

I do configure logging a bit. Let me see if that's related.

No problem, thanks for helping out

Sure. I was totally unaware so thanks for reporting.

Meanwhile I will look into it too, maybe this yet-to-be-a-junior will spot something )

Sure, no pressure! The things I'm asking myself are... 1. Is this ktor? Can I repro it in normal ktor projects? Or is it something in my code? 2. Is this related to my specific version of ktor? Does upgrading fix it? 3. (After seeing the

logback

thread name) Is this related to how I'm configuring logback? 4. How bad is this really? Is this actually resulting in significant performance degradation that people would notice without using profiling tools?

Can I dm you ?

If you want to play with code itself, you can sync kobweb

git clone <https://github.com/varabyte/kobweb>

, go into

playground/site

, and run

kobweb run

in there. That way, you can actually change code under

backend/server/

, quit, and rerun, to see if things are still happening.

I've already been debugging the server