<div dir="ltr"><div class="gmail_extra">2013/4/12 Ilya Volodarsky <span dir="ltr"><<a href="mailto:ilya@segment.io" target="_blank">ilya@segment.io</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>1. What is a recommended amount of subscriptions per channel?</div></div></blockquote><div><br></div><div style>Channels are just integers on the wire and a little bit of state on the node you are connecting to.</div>
<div style>It's unlikely to cause any issues.</div><div style><br></div><div style>Error handling is per-channel so it's a better idea to have one channel per consumer than multiple</div><div style>ones.</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>2. Should we avoid having so many queues? (one queue per project design)</div></blockquote></div><br>Only real workload will tell but generally on multi-core machines it is a better idea to have more queues</div>
<div class="gmail_extra">than a few very heavily congested ones.<br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>