[Node manager] Uses huge amount of RAM on AWS
|Status:||In Progress||Start date:|
|Velocity based estimate||-|
When node manager starts on AWS, it quicky uses a huge amount of RAM (2 GiB) despite not doing anything.
I've tracked this down to
arvnodeman.computenode.driver.ec2.ComputeNodeDriver._init_image_id which calls
libcloud.compute.drivers.ec2.BaseEC2NodeDriver.list_images. It seems that the problem is (a) it is listing a huge number of images (many thousands) and (b) it is retaining a lot of memory even for image records that should be GC'd.
We are currently using libcloud 0.16 on AWS which is an very out of date version.
#3 Updated by Tom Morris 12 months ago
The current version of libcloud is 1.2.1. We should definitely not be using a <1.0 release when 1.0+ is available.