Brett,

I’ve opened a new issue for this on GH, 
https://github.com/couchbase/sync_gateway/issues/768 
<https://github.com/couchbase/sync_gateway/issues/768>, so let’s move the 
conversation over there.

There rest of the response is there.

Best,
Zack

> On Apr 2, 2015, at 5:42 PM, Brett Harrison <[email protected]> 
> wrote:
> 
> 1.  I was wrong about the 500,000 sessions.  Those were 500,000 sessions 
> since HAProxy was started (started on March 25th).
> The sync_gateway has crashed and restarted since then.  The last time it 
> restarted was 2 days and 12 hours ago, so the current running instance of the 
> sync_gateway has not handled all of those sessions.  It has handled 2.5 days 
> of traffic now.
> 
> 2 and 3 these number came from the couchbase server dashboard (gets per sec) 
> and (sets per sec).  
> I have not changed any of the documents in 5 days.  The only time the 
> documents change is when I change them with the REST protocol by using the 
> admin port.
> The app users only pull the documents.  Basically all the documents are read 
> only on the app.  I'm not sure why the couchbase server is showing any writes 
> and assumed that the sync_gateway was saving little documents periodically.
> 
> 4.  To get the current connections I used lsof -p <pid> | grep -i established 
> | wc -l on the sync_gateway server.
> 
> A new update to my app went live in the app store (yesterday) where I changed 
> the Puller to not use continuous mode, so I expect less traffic on the 
> sync_gateway going forward.  That would mean less connections.
> 
> Memory usage continues to increase however.
> 
>                               total       used       free     shared    
> buffers     cached
> 
> Mem:       6153524    4030928    2122596        216     152852     242036
> 
> From the top command...
> 
>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND   
>                                                                               
>                     
> 
>       538 root      20   0 4085080 3.365g   5960 S   1.0 57.3  80:19.47 
> sync_gateway
> 
> compare to my earlier top
> 
>       538 root      20   0 3765652 2.349g   5960 S   1.3 40.0  35:11.40 
> sync_gateway 
> 
> It's now using 57% of the memory where before it was using 40%
> 
> 
> 
> 
> On Thursday, April 2, 2015 at 3:18:13 PM UTC-7, Adam Fraser wrote:
> I don't know of any current issues with memory usage related to attachments.
> 
> I'm not sure I completely understand your environment usage, based on your 
> notes.  Can you confirm the following?
> 
> 1. A server that has been up for a day or two has had 500,000 sessions in 
> that time
> 2. Each sync gateway node averages 85 reads/sec
> 3. Each sync gateway node averages less than one write per second - and zero 
> writes in the last five days?
> 4. You only have 94 open connections
> 
> In particular, how does the 500k number from #1 align with the 94 number from 
> #4?  How are you measuring the number of connections?
> 
> Thanks,
> Adam
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Couchbase Mobile" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/mobile-couchbase/880c1f2a-86e9-415e-98a3-4f29028948d3%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/mobile-couchbase/880c1f2a-86e9-415e-98a3-4f29028948d3%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/3F227579-7048-482E-AFCF-1E973B949DEE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to