search for: anything_really

.... The problem seems to be that just by accessing to the model attribute that has the uploader mounted, Carrierwave seems to be hitting the disk to either read the file, check that it exists, or something. In other words, calling: user.avatar user.avatar.cropped user.avatar.present? user.avatar.anything_really All of these hit the HDD. In the worst case I found, for one of our clients that have a massive amount of data, the page renders in 10 seconds my dev machine, and 30 seconds on the server. This page render implies about 1200 calls to "user.avatar.cropped". The difference seems to be...