Homelab

371 readers

3 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis

can somebody(linux crack) confirm or dement this statement? (alien.top)

submitted 1 year ago by Ordinary-Mistake-279@alien.top to c/homelab@selfhosted.forum

6 comments fedilink hide all child comments

i just read now a article about hardcoded scaling on linux, which is a maximum of 8 cores (or maybe even threads?) a few days ago also read that the cpu scheduler get's an overhaul so i hope they fix this issue, too. Article: https://thehftguy.com/2023/11/14/the-linux-kernel-has-been-accidentally-hardcoded-to-a-maximum-of-8-cores-for-nearly-20-years/

you are viewing a single comment's thread
view the rest of the comments

[–] anothercorgi@alien.top 1 points 1 year ago

If this had been a real issue, it should have been detected quite a while ago. However as far as I can tell, this limit is reached if one is running very very quick running programs, say if it only takes 5ms to fork and run the program, then one may run into this 8 core issue.

This will basically slow down poorly written shell scripts that constantly runs subprograms - if the subprograms run in parallel (which they are not unless multiple instances of the script are running at the same time). Also it means fork bombs will create processes slower than expected on machines with more then 8 processors. I highly doubt someone would worry about this case.