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

Pass over Action Cable docs #24850

Merged
merged 1 commit into from
May 21, 2016
Merged

Conversation

maclover7
Copy link
Contributor

[ci skip]

#
# Using Active Record, Redis, etc within your channel actions means you'll get a separate connection from each thread in the worker pool.
# Plan your deployment accordingly: 5 servers each running 5 Puma workers each running an 8-thread worker pool means at least 200 database
# connections.
#
# Also, ensure that your database connection pool size is as least as large as your worker pool size. Otherwise, workers may oversubscribe
# the db connection pool and block while they wait for other workers to release their connections. Use a smaller worker pool or a larger
# db connection pool instead.
# the datbase connection pool and block while they wait for other workers to release their connections. Use a smaller worker pool or a larger
Copy link
Contributor

@kaspth kaspth May 4, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dat base are belong to us ( ͡° ͜ʖ ͡°)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's still a typo here ;)

@kaspth
Copy link
Contributor

kaspth commented May 21, 2016

Otherwise 👍

@maclover7
Copy link
Contributor Author

👍 thanks for the review!

@maclover7 maclover7 merged commit 5ec889e into rails:master May 21, 2016
@maclover7 maclover7 deleted the jm-actioncable-docs branch May 21, 2016 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants