This one has me stumped. We are using couch for our session data and inactive items are set to expire after 2 hours. We have about 11k items, each being about 2k or less.. We see items being cleaned every hour, yet Memory Used keeps going up no matter what?!
Ops per second: 6-13 Memory used: 550M !! High Water: 471M Low Water: 337M Items: 11.2k Avg Image Size: 2k User data in RAM: 1.51M Meta data in RAM: 25.6M
On 10/10/12 11:36 AM, "Josh Deltener" <josh.delte...@realtruck.com<mailto:josh.delte...@realtruck.com>> wrote:
This one has me stumped. We are using couch for our session data and inactive items are set to expire after 2 hours. We have about 11k items, each being about 2k or less.. We see items being cleaned every hour, yet Memory Used keeps going up no matter what?!
Ops per second: 6-13
Memory used: 550M !!
High Water: 471M
Low Water: 337M
Items: 11.2k
Avg Image Size: 2k
User data in RAM: 1.51M
Meta data in RAM: 25.6M
What's the quota and where are these stats coming from? Which platform?
Do be aware that generally the way memory allocation works is that processes don't shrink their memory usage later. I believe couchbase does actually try to return memory, but this will be based on how the actual memory is laid out. We leverage tcmalloc on Linux, for example.
On Wednesday, October 10, 2012 at 2:57 PM, Matt Ingenthron wrote:
> On 10/10/12 11:36 AM, "Josh Deltener" <josh.delte...@realtruck.com (mailto:josh.delte...@realtruck.com)> wrote:
> > This one has me stumped. We are using couch for our session data and inactive items are set to expire after 2 hours. We have about 11k items, each being about 2k or less.. We see items being cleaned every hour, yet Memory Used keeps going up no matter what?!
> > Ops per second: 6-13
> > Memory used: 550M !!
> > High Water: 471M
> > Low Water: 337M
> > Items: 11.2k
> > Avg Image Size: 2k
> > User data in RAM: 1.51M
> > Meta data in RAM: 25.6M
> What's the quota and where are these stats coming from? Which platform?
> Do be aware that generally the way memory allocation works is that processes don't shrink their memory usage later. I believe couchbase does actually try to return memory, but this will be based on how the actual memory is laid out. We leverage tcmalloc on Linux, for example.
On Wednesday, October 10, 2012 at 3:07 PM, Aliaksey Kandratsenka wrote:
> On Wed, Oct 10, 2012 at 12:06 PM, Chad Kouse <c...@tunewiki.com> wrote:
> > On Linux I was able to free the buffer cache using this command:
> > sync && echo 3 > /proc/sys/vm/drop_caches
> Which is actually bad idea to do. Top will tell you which memory is
> used by programs and which by page cache and other kernel caches.
On Wed, Oct 10, 2012 at 12:12 PM, Chad Kouse <chad.ko...@gmail.com> wrote:
> Is it a bad idea for performance reasons or is there potential for data
> loss/corruption? I used to do it all the time.
Performance reasons.
It's purpose is to get you 'cold' system i.e. for benchmarking. AFAIK
it was never intended for production use.
On Wednesday, October 10, 2012 at 3:15 PM, Aliaksey Kandratsenka wrote:
> On Wed, Oct 10, 2012 at 12:12 PM, Chad Kouse <chad.ko...@gmail.com> wrote:
> > Is it a bad idea for performance reasons or is there potential for data
> > loss/corruption? I used to do it all the time.
> Performance reasons.
> It's purpose is to get you 'cold' system i.e. for benchmarking. AFAIK
> it was never intended for production use.
> Do be aware that generally the way memory allocation works is that > processes don't shrink their memory usage later. I believe couchbase does > actually try to return memory, but this will be based on how the actual > memory is laid out. We leverage tcmalloc on Linux, for example.
On Wednesday, October 10, 2012 2:17:45 PM UTC-5, Josh Deltener wrote:
> 600M quota. Linux, Server 1.8, PHP, this is a couchbase bucket. I'm > getting these numbers from the web interface.
> We are now getting some OOM errors, even though the max ram we SHOULD be > using is around 45M. It's like it's not flushing any items that have > expired.
> What's the quota and where are these stats coming from? Which platform?
>> Do be aware that generally the way memory allocation works is that >> processes don't shrink their memory usage later. I believe couchbase does >> actually try to return memory, but this will be based on how the actual >> memory is laid out. We leverage tcmalloc on Linux, for example.
Yesterday, we nuked this Couchbase bucket and moved it over to a Memcache bucket. It's confirmed, we never go above 10M of data and never above 12k items.. So why on earth would a Couchbase bucket suck up 550M! I should mention we are still having similar issues with our other Couchbase buckets.
I looked through your post and it appears that your bucket is not writing items to disk. Have you disabled persistence? If not can you upload you logs for me to look at? Instructions for how to do this can be found here:
On Thursday, October 11, 2012 5:56:52 AM UTC-7, Josh Deltener wrote:
> Yesterday, we nuked this Couchbase bucket and moved it over to a Memcache > bucket. It's confirmed, we never go above 10M of data and never above 12k > items.. So why on earth would a Couchbase bucket suck up 550M! I should > mention we are still having similar issues with our other Couchbase buckets.
It's writing to disk. We have a bunch of data on disk and items in/out of the write queue. We used Couchbase out of the box and haven't configured anything funky. I'll try to gather some logs for you.
On Thursday, October 11, 2012 6:38:50 PM UTC-5, Mike Wiederhold wrote:
> I looked through your post and it appears that your bucket is not writing > items to disk. Have you disabled persistence? If not can you upload you > logs for me to look at? Instructions for how to do this can be found here:
> On Thursday, October 11, 2012 5:56:52 AM UTC-7, Josh Deltener wrote:
>> Yesterday, we nuked this Couchbase bucket and moved it over to a Memcache >> bucket. It's confirmed, we never go above 10M of data and never above 12k >> items.. So why on earth would a Couchbase bucket suck up 550M! I should >> mention we are still having similar issues with our other Couchbase buckets.