Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96870DC42 for ; Thu, 18 Oct 2012 14:36:03 +0000 (UTC) Received: (qmail 4739 invoked by uid 500); 18 Oct 2012 14:36:03 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 4719 invoked by uid 500); 18 Oct 2012 14:36:03 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 4706 invoked by uid 99); 18 Oct 2012 14:36:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2012 14:36:03 +0000 Date: Thu, 18 Oct 2012 14:36:02 +0000 (UTC) From: "Michal Fojtik (JIRA)" To: dev@deltacloud.apache.org Message-ID: <1230135013.64123.1350570963265.JavaMail.jiratomcat@arcas> In-Reply-To: <351698185.57693.1350480724009.JavaMail.jiratomcat@arcas> Subject: [jira] [Comment Edited] (DTACLOUD-347) Deltacloud API leaking memory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DTACLOUD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478996#comment-13478996 ] Michal Fojtik edited comment on DTACLOUD-347 at 10/18/12 2:34 PM: ------------------------------------------------------------------ I tried to use 'webrick' (not thin), same results (actually the overall memory footprint went down from 140MB (thin) to 32MB (webrick)). was (Author: mfojtik): I tried to use 'webrick' (not thin), same results (actually the over memory footprint went down from 140MB (thin) to 32MB (webrick)). > Deltacloud API leaking memory > ----------------------------- > > Key: DTACLOUD-347 > URL: https://issues.apache.org/jira/browse/DTACLOUD-347 > Project: DeltaCloud > Issue Type: Bug > Components: Server > Environment: deltacloud-core, GIT adade32451815c8ee28e29be35636bd0f98473fc > Reporter: Michal Fojtik > Priority: Blocker > Labels: blocker-1.0.5 > > Deltacloud API memory usage is slowly increasing after doing 100+ requests: > Starting Deltacloud API :: mock :: http://localhost:3001/api > >> Thin web server (v1.5.0 codename Knife) > >> Debugging ON > >> Maximum connections set to 1024 > >> Listening on localhost:3001, CTRL+C to stop > 127.0.0.1 - - [17/Oct/2012 15:26:10] "GET /api/images HTTP/1.1" 200 4420 0.0308 > 127.0.0.1 - - [17/Oct/2012 15:26:17] "GET /api/images HTTP/1.1" 200 4420 0.0220 > 127.0.0.1 - - [17/Oct/2012 15:26:52] "GET /api/images HTTP/1.1" 200 4420 0.0219 > ... 1000 requests after: > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1539 > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1554 > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1526 > As you can see the response time is slowly increasing and after few minutes it gets to the point where the request take like 10 seconds to complete and all your free memory is gone ;-) > This is easy to reproduce: > 1. Start Deltacloud API ($ deltacloudd -i mock) > 2. $ while true; do curl -H 'Accept: application/xml' --user 'mockuser:mockpassword' http://localhost:3001/api/images > /dev/null; done > 3. Keep it running for ~1minute and watch the console with Deltacloud API log. > Thanks to Tomas Hrcka for reporting this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira