🤗 [Question]: How does the prefork in Fiber work?

[hitrop]

Question Description

Fasthttp github page suggests a series of steps to improve the performance on multi-core systems (https://github.com/valyala/fasthttp?tab=readme-ov-file#performance-optimization-tips-for-multi-core-systems)

• Use reuseport listener.
• Run a separate server instance per CPU core with GOMAXPROCS=1.
• Pin each server instance to a separate CPU core using taskset.
• Ensure the interrupts of multiqueue network card are evenly distributed between CPU cores. See this article for details.
• Use the latest version of Go as each version contains performance improvements.

Does go fiber perform these steps in the prefork option?

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my questions prior to opening this one.
• I understand that improperly formatted questions may be closed without explanation.

[welcome]

Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

[nickajacks1]

Prefork will cause fiber to

• use 1 cpu core per process
• use SO_REUSEPORT or SO_REUSEADDR depending on the platform

It doesn't look like CPU affinity is set by Fiber when prefork is enabled. It also doesn't look like the child PIDs are directly exposed for you to set the affinity yourself either. That would need to be added to the App API somehow.

Adjusting interrupts must be done manually.

[gaby]

Duplicate of #180

[ReneWerner87]

@hitrop does it answer your question?