couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Rempe <>
Subject Re: Timeout Error when trying to access views + Indexing problems
Date Tue, 06 Oct 2009 23:15:01 GMT
Paul wrote a little script to help me out with tracking mem.  Alas, he
didn't realize it wasn't attached until he was away from his computer.

I whipped up a little ruby version if its useful to anyone.

Just pass it a PID as a param and it will print out the newest
highwater memory mark for that process and a timestamp.



On Tue, Oct 6, 2009 at 1:13 PM, Paul Davis <> wrote:
> On Tue, Oct 6, 2009 at 3:42 PM, Glenn Rempe <> wrote:
>> Is there some way we can instrument and log how much memory the VM
>> thinks it has somewhere in the critical path piece of erlang code?  Or
>> is there another way I can track that externally?
>> G
>> On Tue, Oct 6, 2009 at 12:13 PM, Adam Kocoloski <> wrote:
>>> On Oct 6, 2009, at 2:46 AM, Glenn Rempe wrote:
>>> TMI logging doesn't really exist, no one uses that level internally.  I
>>> agree with Paul here, the lack of error messages indicates an instant VM
>>> death.  The most common way to cause that is by running out of memory, but
>>> view indexing is not supposed to use a large amount of memory at all.
>>> Adam
> Here's a quick and dirty script that should work ish I think probably.
> I only tested it minimally. As it, no syntax errors and it prints the
> first vm size as expected.
> Just run that in a terminal while the indexer runs. It should die at
> the same time the the Erlang process dies.

Glenn Rempe

email                 :
voice                 : (415) 894-5366 or (415)-89G-LENN
twitter                : @grempe
contact info        :
pgp                    :

View raw message