We were trying the new config_loader option by passing a lambda, but we see that the Resident Set Size (RSS) of the resque-pool doubles within an hour. When we start the resque-pool, the size was around 500MB but within an hour, the size is above 1G. Without using the config_loader, the RSS remains stable (around the initial size). It seems like whatever object that was created/used within the lambda block is not being GCed.
We were trying the new config_loader option by passing a lambda, but we see that the Resident Set Size (RSS) of the resque-pool doubles within an hour. When we start the resque-pool, the size was around 500MB but within an hour, the size is above 1G. Without using the config_loader, the RSS remains stable (around the initial size). It seems like whatever object that was created/used within the lambda block is not being GCed.