Right it's mostly useful for append only operations like cdr writing. Of course you'll be able to do alot of that via the acc module, but this lets you write all sorts of other analytics at high insertion rate as well.<div>
<div><br></div><div>Oh and speaking of append only... Couchbase does support an "append" method that would be nice to expose to the script as well. :)</div><div><br></div><div>Thanks for your time Vlad,</div><div>
Brett</div><div><br></div><div><br><div class="gmail_quote">On Tue, Feb 12, 2013 at 10:24 AM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org" target="_blank">vladpaiu@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Brett,<br>
<br>
While Couchbase supports such operations, I can't see that other familiar NoSQL back-ends support such multiset features.<br>
Could you give more examples of back-ends supporting this ?<br>
<br>
Also, it might be that doing delayed inserts for cache operations would lead to some tricky scenarios.. Like if you want to cache some information from a regular DB, you will end up first loading the info and storing it in memory, in order to do a multiset later when more set queries have piled up.<br>
Then when you'd need the key again, you would not find it ( since it's still in mem waiting to be flushed to the back-end ) and again fetch it from the DB and put it into memory waiting for the multi set. So it kind of breaks the cache concept ( that once you put something there, you'll find it next time ).<br>
<br>
Regards,<br>
<br>
Vlad Paiu<br>
OpenSIPS Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><div><div class="h5"><br>
<br>
<br>
On 02/10/2013 11:17 PM, Brett Nemeroff wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hey all,<br>
Quick feature request. Many of the cache back ends support multisets<br>
at once. I've seen tremendous speed improvements from multisets. In<br>
addition, maybe complementary, I'd like to see queues cache<br>
insertions. This is especially useful for using the cache interface<br>
for something like acc. The idea would be that it'll queue up<br>
insertions (set/add) nd maybe in a timer route or when some queued<br>
message count is hit, it'd multiset all if them at once. Doing one set<br>
with thousands of records is much faster than multiple connections to<br>
do the same<br>
<br>
Thanks!<br>
Brett<br>
<br>
-Brett<br>
<br></div></div>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div></div>