• A Look at Common Performance Problems in Rails
  A Look at Common Performance Problems in Rails
  Rails performance expert Dr. Stefan Kaes takes a look at the most common performance issues in your Rails applications and what to do about them. Advice is given regarding benchmarking, choosing a session container, caching results of expensive computations, optimizing database queries and working effectively with view helpers.
  architecture design development evaluation frameworks memcache performance rails ruby scalability web
  in Rails with performance rails by 3 users
• Dynamic Reflection Library
  * Why would I use this? 1. If you need to do binding of code to fields/proporties/methods in classes dynamically, but want full type-safety and excellent performance. This means that you can, with a 25% or less overhead, bind to methods using the method name (or MemberInfo). This compares using standard Reflection, which is typically 20x slower or worse. 2. If you want to muck about in private members/methods of a sealed or poorly designed class that you don't have source for (e.g. to fix problems in a .Net framework class). 3. If you don't have the ability to dictate an interface, but can dictate a (type-compatible) method signature. 4. If you are allowing users to specify classes, methods or sort criteria at runtime
  in .NET with dynamical net performance reflection type-safety

performance from all users