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
10gen MMS
Home
+ new post
About this group
Join this group
Message from discussion Memory Leak
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
 
Jose Neto  
View profile  
 More options Mar 7 2012, 8:31 am
From: Jose Neto <jbastosn...@gmail.com>
Date: Wed, 7 Mar 2012 05:31:19 -0800 (PST)
Local: Wed, Mar 7 2012 8:31 am
Subject: Re: Memory Leak
Print | View thread | Show original | Report this message | Find messages by this author

I have the same problem while using pypy (no C extensions) and using
the find_one method over and over. It will leak gigabytes of memory, over
my 200Mb dataset.
While using the same code on python 2.7 (with C extensions), the problem
goes away.
Is there any workaround? It seems looks the cursors are leaking memory.

On Friday, February 24, 2012 2:53:18 PM UTC-2, John Nunemaker wrote:

> I installed mms on a slave database. From there it talks to both
> master/slave. We have pretty consistently been seeing the mms-agent grab
> almost all the available memory. Probably happens like 5-10 times a day.

> http://cl.ly/EV04

> Anyone else having issues with this? Anything else I can provide to help
> track this down?


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google