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.

Sign up for GitHub

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

Jump to bottom

routing through shmipc "twice" within itself generates Syscall6 issues #35

Closed
kolinfluence opened this issue Jul 2, 2023 · 3 comments
Closed

routing through shmipc "twice" within itself generates Syscall6 issues #35

kolinfluence opened this issue Jul 2, 2023 · 3 comments

Comments

@kolinfluence
Copy link

i'm not sure how to explain this but i'm using shmipc within a process twice, as both server and client.

under heavy use, this is the issue. how to resolve?

screen161
@goodbye-babyer
Copy link
Contributor

i'm not sure how to explain this but i'm using shmipc within a process twice, as both server and client.

under heavy use, this is the issue. how to resolve?

screen161

The meaning of this SVG image is not clear on its own and requires a specific context and business logic to understand.

@hiqsociety
Copy link

@goodbye-babyer i realised that if you have 2 or more listening and connecting shmipc-go, if you do heavy read / write + some other processes e.g. rocksdb, you will oom

@hiqsociety
Copy link

@goodbye-babyer can you check this?

Screenshot from 2023-07-21 07-29-28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@goodbye-babyer @hiqsociety @kolinfluence