Hi Brett,
While Couchbase supports such operations, I can't see that other
familiar NoSQL back-ends support such multiset features.
Could you give more examples of back-ends supporting this ?
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.
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 ).
Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 02/10/2013 11:17 PM, Brett Nemeroff wrote:
Hey all,
Quick feature request. Many of the cache back ends support multisets
at once. I've seen tremendous speed improvements from multisets. In
addition, maybe complementary, I'd like to see queues cache
insertions. This is especially useful for using the cache interface
for something like acc. The idea would be that it'll queue up
insertions (set/add) nd maybe in a timer route or when some queued
message count is hit, it'd multiset all if them at once. Doing one set
with thousands of records is much faster than multiple connections to
do the same
Thanks!
Brett
-Brett
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
