search

rnjacobs / wmbubble

(official) maintained fork of timecop's bubblemon-dockapp
9 stars 5 forks source link

consider multiple ducks, one per CPU #9

Open jmtd opened 5 years ago

jmtd commented 5 years ago

I think this would be a nice (optional) feature to illustrate the number of cores/vcpus visible to the machine (virtual or otherwise) running wmbubble.

rnjacobs commented 5 years ago

Even though the ducks are purely decorative? It'd literally just be "X ducks = X logical cores available" ?

Is CPU hotplug a thing that I should support, or can I just check at startup? I ask because historically, one of the biggest contributors to CPU load is asking the kernel to generate the special files in /proc

jmtd commented 5 years ago

Thanks for your reply!

Even though the ducks are purely decorative? It'd literally just be "X ducks = X logical cores available" ?

Yes

Is CPU hotplug a thing that I should support, or can I just check at startup? I ask because historically, one of the biggest contributors to CPU load is asking the kernel to generate the special files in /proc

That's a good question. I am no expert on CPU hotplugging, but this suggests that you could register for udev events, but that would probably mean extending the dependencies of the program to include udev integration.

For an optional extention to a purely decorative feature, I'd be inclined to statically determine the number of CPUs at start up only and leave it at that.