Poor database performance is a thing at my current gig. But often the only solution is having a custom view made.
Sometimes.
But I'd urge you -and every Rails dev struggling with this- to look at how and where you can decouple and separate the concerns in your (quite likely) ball-of-models.
Most often that is a far more sustainable solution. One that helps you not only with performance.