Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mongodb as cache leyer
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
mongoUser1  
View profile  
 More options Oct 18 2012, 12:55 pm
From: mongoUser1 <ynotfried...@gmail.com>
Date: Thu, 18 Oct 2012 09:55:47 -0700 (PDT)
Local: Thurs, Oct 18 2012 12:55 pm
Subject: mongodb as cache leyer

Hi ,

we are using MongoDB currently as replica Set to Sync data between our data
centers .
to speed up performance we need to implement some kind of cache layer .
we currently considering memcahed & mongodb .
the data stored in the cache is key-value type , with small size strings .
the cache should be distributed at the data center between computers there .
we have mongo version 2.0 and not 2.2 where the TTL collections exists , so
we implemented it by a thread that remove old entries after the TTL .
we expect the cache size to be ~10 milion records .
and we expect the cache to be queried ~1000 times a second .
will the mongoDB holds in this kind of hit rate , where the same collection
will be scaned very often with reads , and written too (in smaller scale) ,
and deleted from ?
won't the memcached solution per data center be better in performance?
this way the primary won't be written at all (just from our MS-SQL DB , not
from the side of the clients),
and the queries to my understanding will be faster (am i right?)
i hesitate to add another layer of the memcached , and if the mongoDB will
handle it i gladly will choose it .

thanks.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Max Schireson  
View profile  
 More options Oct 19 2012, 4:27 am
From: Max Schireson <mschire...@gmail.com>
Date: Fri, 19 Oct 2012 01:26:41 -0700
Local: Fri, Oct 19 2012 4:26 am
Subject: Re: [mongodb-user] mongodb as cache leyer

~1000 per second over 10 million records sounds well within range of course
hard to say for sure without more details, but plenty of folks do more than
that even on a single box.

2.2 handles mixed read/write workloads better; i'd consider that upgrade
unless the writes are extremely infrequent.

-- Max
On Oct 18, 2012 9:55 AM, "mongoUser1" <ynotfried...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »