Comment by ElCapitanMarkla
19 hours ago
I started to notice this in a big way at my last job which I started in 2013. We were a rails shop and by about 2016 I was noticing most new hires would have no idea how to write a SQL query.
19 hours ago
I started to notice this in a big way at my last job which I started in 2013. We were a rails shop and by about 2016 I was noticing most new hires would have no idea how to write a SQL query.
> most new hires would have no idea how to write a SQL query.
probably why people think rails is slow. our integration partners and our customers are constantly amazed by how fast and efficient our system is. The secret is I know how to write a damn query. you can push a lot of logic that would otherwise be done in the api layer into a query. if done properly with the right indexes, its going to be WAY faster than pulling the data into the api server and doing clumsy data transformations there.
1000%. It’s all about limiting those round trips to the database…
You actually confirmed that rails is slow if the optimization is on the database server and doing data mangling in ruby is less efficient
Constructively, I would suggest some areas for study:
- relative speeds of programming languages (https://news.ycombinator.com/item?id=39658138)
And note that databases are generally written in C.
1 reply →
Unless the database is in your process's address space (SQLite, Datomic, etc) your first problem is going to be shipping the data from the database server to the application process.
You've correctly identified that filtering a list is slower than looking up from an index. Congratulations.
1 reply →