Calling update_rates without a cache file on a puma cluster pins CPU threads to 100%.

[joshuapinter]

Prior to setting up a cache file to store the latest currency exchange rates and just have them updated on a daily basis, we were just doing update_rates on our money.rb initializer.

After the first request, all of the puma workers (that were called) became pinned at 100% CPU usage so this is what our development machine's htop looked like at idle after the first few requests:

I went down a rabbit hole with puma, thinking it must be the culprit, but it was actually just calling update_rates that caused this. Here is a comparison of what changes between this issue being present or not.

Issue Present

eu_central_bank = EuCentralBank.new

eu_central_bank.update_rates

config.default_bank = eu_central_bank

Issue NOT Present

eu_central_bank = EuCentralBank.new

eu_central_bank.update_rates( Rails.root.join( "rates.xml" ) )

config.default_bank = eu_central_bank

We've moved on by just using a cache file but I wanted to post this here because I searched and I didn't find any Issues documenting this.

[semmons99]

@joshuapinter can you check if #110 solves your issue?

[joshuapinter]

@semmons99 You bet. I'll try and take a look this weekend.

[joshuapinter]

Sorry for the delay. I'll take a look this week to confirm.

[joshuapinter]

To confirm, I upgraded to 1.7.0 and don't run into the issue, so I think it is now resolved. Thanks for handling and happy holidays! 🎄

[semmons99]

great. thank you!