-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: messenger improve latency #108
feat: messenger improve latency #108
Conversation
f72b5b9
to
38496b7
Compare
@@ -93,6 +93,10 @@ pub struct Configuration { | |||
pub allowed_actions: HashMap<String, Vec<String>>, | |||
/// Channel buffer size for the internal channels between threads | |||
pub channel_buffers: Option<ChannelBuffers>, | |||
/// Commit size to decide how often the certifier topic can be committed by the consumer. | |||
/// The more ofter the commit is done has inverse impact on the latency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A small typo
|
||
}, | ||
MessengerChannelFeedback::Success(version, key) => { | ||
info!("Successfully processed version={version} with action_key={key}"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be debug instead of info, to reduce a noise in the log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that suffix logic was updated, I wonder if we need to update unit tests as well.
The base suffix hasn't changed. Messenger uses the base suffix from |
No description provided.