Skip to content

Fix grammar errors #9

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

Merged
merged 1 commit into from
Feb 13, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions credit_flow.md
Original file line number Diff line number Diff line change
Expand Up @@ -226,8 +226,8 @@ messages (between acks + messages paged from the cache). The messages
that were paged out just had their contents paged out, but their
position in the queue is still in RAM. Now the queue needs to decide
if this extra information that’s kept in RAM needs to be paged out as
well, to further reduce memory usage. Here is were finally
`msg_store_io_batch_size` enters into play (coupled with
well, to further reduce memory usage. Here is where
`msg_store_io_batch_size` finally enters into play (coupled with
`msg_store_credit_disc_bound` as well). Let’s try to understand how
they work.

Expand All @@ -241,7 +241,7 @@ and disks.
The message store has a credit system for each of the clients that
send writes to it. Every RabbitMQ queue would be a read/write client
for this store. The message store has a credits mechanism to prevent a
particular writer to overflow its inbox it with messages. Assuming
particular writer to overflow its inbox with messages. Assuming
current default values, when a writer starts talking to the message
store, it receives an initial credit of 2000 messages, and it will
receive more credit once 500 messages are processed. When is this
Expand Down