From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org> Subject: Re: How to manage growing memory with Rainbows! Date: Thu, 14 Feb 2013 20:28:28 +0000 [thread overview] Message-ID: <20130214202828.GB23895@dcvr.yhbt.net> (raw) In-Reply-To: <F6728D3D-3E35-488B-8165-EB80E25FFF1B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Claudio Poli <claudio-3HQ/CcOImoi171pxa8y+qA@public.gmane.org> wrote: > I have few more questions before definitely make the switch if you don't mind. > > ActiveRecord/Redis. > This is the configuration I'm trying out in staging: http://pastie.org/private/zepmdeduvlrvtdkc32unnq > > Is there something special that should I know about AR connection pool and Rainbows! + Threadpool? My pool in database.yml is 30. As long as your database can handle the number of connections you have, you're probably fine. Keep in mind you'll have 30 connections per-process (not per-thread), so take that into account if you need to change the process count or start an upgrade with SIGUSR2. > After a small load test currently I'm sitting around 60/80 connections, which is kinda expected given that also Sidekiq is in action. > > I don't like the global $redis connection. Can you, or anyone else, offer any advice how to improve that, if you use it in your projects? > The goal was to keep a connection alive in a single process due to the sheer number of commands that can be put in redis as consequence of actions, but now that I'm using threads it probably needs to be changed. > The cost however for opening a new connection seems high, I was reading this: https://groups.google.com/forum/?fromgroups=#!topic/redis-db/xcz5MXykXdk I have no experience using Redis, but I know it's a TCP-based service. The easiest might be a Thread-local connection with ThreadPool: def redis Thread.current[:my_app_redis] ||= Redis.new(url: url) end This won't work well for ThreadSpawn. _______________________________________________ Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2013-02-14 20:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-12 4:19 Claudio Poli [not found] ` <E326380F-0B96-4B17-B721-DB814415E03E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2013-02-12 5:00 ` Eric Wong [not found] ` <20130212050021.GA18443-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org> 2013-02-14 6:58 ` Claudio Poli [not found] ` <B3ED3231-62E8-4FF5-A65A-859AFD790C2B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2013-02-14 7:15 ` Eric Wong [not found] ` <20130214071512.GA10890-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org> 2013-02-14 8:49 ` Claudio Poli [not found] ` <F6728D3D-3E35-488B-8165-EB80E25FFF1B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2013-02-14 20:28 ` Eric Wong [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://yhbt.net/rainbows/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20130214202828.GB23895@dcvr.yhbt.net \ --to=normalperson-rmlxzr9ms24@public.gmane.org \ --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \ --subject='Re: How to manage growing memory with Rainbows'\!'' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: ../../rainbows.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).