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

Add "quick turn" in dataservice implementation #86

Open
jphickey opened this issue Apr 8, 2022 · 0 comments
Open

Add "quick turn" in dataservice implementation #86

jphickey opened this issue Apr 8, 2022 · 0 comments
Labels
defer No action is expected to be taken enhancement New feature or request

Comments

@jphickey
Copy link
Collaborator

jphickey commented Apr 8, 2022

When using a storage storage service attached to a data service node that also has local application endpoints/sockets, bundles that get pulled from storage end up on the ingress queue. Therefore it becomes common to get bundles in the ingress queue which are actually destined for the same data service.

These bundles will traverse the routing table and will be delivered back to the egress queue of the same service.

This is really just an optimization concern, the flow works as-is but might be a little more expensive/roundabout than it needs to be. The data service ingress routine could check for this possibility, and turn it around immediately, without going to the central routing table.

This is low priority for now, because it does work as is, and things may change again before this becomes a performance concern.

@jphickey jphickey added defer No action is expected to be taken enhancement New feature or request labels Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defer No action is expected to be taken enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant