Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

use a heuristic to determine whether or not to use asynchronous publishing #190

Closed
wjwwood opened this issue Jul 5, 2016 · 1 comment
Closed
Labels
enhancement New feature or request

Comments

@wjwwood
Copy link
Member

wjwwood commented Jul 5, 2016

See: #183 (comment)

The proposal from the linked pull request would be, use synchronous publishing:

  • if the reliability is BEST_EFFORT (type bounded or unbounded)
  • if the reliability is RELIABLE and the type is bounded and the maximum size is less than MAX_SYNC_PAYLOAD

Where MAX_SYNC_PAYLOAD is some maximum size that can be used without asynchronous publishing.

Use asynchronous publishing:

  • if the reliability is RELIABLE and the type is bounded and the maximum size is more than MAX_SYNC_PAYLOAD
  • if the reliability is RELIABLE and the type is unbounded (has no maximum size)

Something else to consider is whether or not messages with unbounded size can always be published with synchronous publishing, even with reliability as BEST_EFFORT.

@clalancette
Copy link
Contributor

Closing, since with Foxy now being End-of-Life, this repository is no longer used.

@clalancette clalancette closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants