Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tested with 192 cores, performance is not very good, suggestion on how to tweak for 192 or 448 cores server #13

Open
ouvaa opened this issue Mar 29, 2024 · 3 comments
Labels
question Further information is requested

Comments

@ouvaa
Copy link

ouvaa commented Mar 29, 2024

wanted to go extreme, how to make 192 cores faster? same pastebin info on server, doesnt really scale that well. can suggest how to make it multicore shard better?

@phuslu
Copy link
Owner

phuslu commented Mar 29, 2024

an issue worth read first golang/go#65064

maybe your bottleneck is on

  1. golang netpoll (as above issue)
  2. golang numa awareness/support (?)

anyway, although sharding processing can resolve this issue but it brings complexity and latency, it still It's a last resort.

@ouvaa
Copy link
Author

ouvaa commented Mar 29, 2024

@phuslu cant believe u found that out and yes i just read it. it's very interesting.
it's actually on gnet using the epoll. everything mentioned by them is valid

i tried thinking in numa actually but found extremely little support. i thought maybe your lru can implement the numa instead

@phuslu phuslu added the question Further information is requested label Mar 30, 2024
@phuslu
Copy link
Owner

phuslu commented Mar 30, 2024

i thought maybe your lru can implement the numa instead

I doubt it because it subject to go scheduler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants