deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-347) Deltacloud API leaking memory
Date Wed, 31 Oct 2012 13:01:12 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487737#comment-13487737
] 

Michal Fojtik commented on DTACLOUD-347:
----------------------------------------

Thanks Ronelle and sorry for the delay, dunno why I thought they were pushed... 

commit b5656392015eb43223bf999474ba61dcab56c6ea
Author: Michal Fojtik <mfojtik@redhat.com>
Date:   Thu Oct 18 21:40:26 2012 +0200

    Replaced YAML.load with YAML.load_file (DTACLOUD-347)
    
    * Fix nasty memory leaking issue under MRI 1.9.3p194
    
    Signed-off-by: Michal fojtik <mfojtik@redhat.com>

commit 03619cf4ea19b0cd7e8c25483d4ec858fbdbfc61
Author: Michal Fojtik <mfojtik@redhat.com>
Date:   Thu Oct 18 21:38:40 2012 +0200

    Added methods to improve memory leaks debugging
    
    Signed-off-by: Michal fojtik <mfojtik@redhat.com>

commit 16b1c280e701701b23668022048bb675e417ebc8
Author: Michal Fojtik <mfojtik@redhat.com>
Date:   Thu Oct 18 21:36:25 2012 +0200

    Make DC compatible with webrick
    
    Signed-off-by: Michal fojtik <mfojtik@redhat.com>


                
> 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
>            Assignee: 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

Mime
View raw message