-
Notifications
You must be signed in to change notification settings - Fork 337
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Different MessageID implementations for message Production and Consum…
…ption (#324) This change splits the `MessageID` implementation in two: 1. `messageID` - A 24 byte structure that contains message identification information only; to be used during message production 2. `trackingMessageID` - A 72 byte structucture that shares the same message identification information as `messageID` and adds `ackTracker`, `acker`, and `receivedTime` fields; to be used during message consumption Micro benchmarks show that passing arguments by value that are less-than four words of memory are optimized by the Go runtime. Results from the pulsar/impl_message_bench_test.go module are below. ``` name time/op ProducerCall 1.46ns ± 5% ProducerCall-4 1.47ns ± 5% ConsumerCall 7.62ns ± 1% ConsumerCall-4 7.53ns ± 5% ``` Co-authored-by: Daniel Ferstay <dferstay@splunk.com>
- Loading branch information
Showing
10 changed files
with
180 additions
and
93 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.