I've had similar experiences. And it's not always Ruby processing being the slow... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

coryodaniel on Nov 26, 2016 | parent | context | favorite | on: Let Postgres Do the Work (2013)

I've had similar experiences. And it's not always Ruby processing being the slow part but returning multiple result sets to your application layer.

I've seen some huge result sets (thousands of rows) returned to do a simple aggregation for a dashboard widget.

phereford on Nov 26, 2016 [–]

Absolutely agreed. In our particular situation, the ruby calculations were the bottlenecks based on our benchmarks.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact