CODEWITHSUNDEEP
ruby-on-railsredispublish-subscribe
AdamNYC
AdamNYC

Reputation: 20415

Using Redis pub/sub creates too many threads

I have a Rails front-end server, which receives multiple requests from users, then send these requests to backend server.

Backend server processes requests asynchronously and notifies front-end server when it finishes each of the requests.

I use Redis pub/sub to communicate between these two servers. In particular, for each request coming from users, I create a new Redis instance that subscribes to the single channel (say, scoring_channel).

However, if I have 100 users making requests at the same time, each of the Redis subscribers will hold one thread.

Does this affect my server performance? If I have a constraint on maximum number of threads (e.g., Heroku allows max 256 threads), how should I avoid this issue?

Upvotes: 0

Views: 1020

Answers (1)

yinqiwen
yinqiwen

Reputation: 659

This would not affect server performance since redis never blocked by pub/sub. You should use non-blocking API in client side instead of blocking version to decrease number of threads.

Upvotes: 1

Related Questions