If you’ve ever built a sizeable Rails app before, you know that efficient cache use can really supercharge your application. The storEDGE platform has always tried to offer the best performance to our users by keeping our memcached processes on the same instances as our application servers. While this is
Today, I came across a puzzling issue with Rails 4.1, ActiveRecord, and Postgres when trying to select random records from a database table. To demonstrate, let’s use a simple social network API example. Clients will POST a list of user, and I’ll “match” them to someone in my database. Easy
While looking at performance optimizations for a rails project, I noticed these lines in my debug console: ActsAsTaggableOn::Tag Load (0.5ms) SELECT “tags”.* FROM “tags” INNER JOIN “taggings” ON “tags”.”id” = “taggings”.”tag_id” WHERE “taggings”.”taggable_id” = $1 AND “taggings”.”taggable_type” = $2 AND (taggings.context = (‘tags’)) [[“taggable_id”, 103], [“taggable_type”, “Prediction”]] This makes sense,