3 ms·
> Perfomance isn't great I would argue that the performance hit isn't from ruby or the framework, but from people abusing the database with lazy loading in act
by ydnaclementine 5y ago
> Perfomance isn't great
I would argue that the performance hit isn't from ruby or the framework, but from people abusing the database with lazy loading in active record. Force people to fetch all the data they need in one query (similar to Ecto), and your performance will improve. There's some config value that disables lazy loading too
- projct 5y agoThis is the most common slowdown I've seen in rails before. strict_loading mode can help, as can the bullet gem. That said, it is also quite slow when you actually do need requests per second or rows per second, but the usual thing is to throw more machines at it,reduce the amount of magic in the hot path (like activerecord-import for bulk data if that's still maintained,) or use something else for the hot path.
- nunez 5y agoTo clarify, performance isn't "great" (i.e. Ruby tends to be slower than writing the same code in, say, Go), but it's good enough for most things.