Nope. You could put it on a beefy machine with a beefy database and it would still crawl a lot of the time. It just had some combination of terrible database querying and general slowness. The whole generic inner-platform effect way it's constructed (e.g. having its own ticket query language that they presumably translate generically into SQL) was probably a big factor.

Not discounting your knowledge, but somehow that was never the case for me across multiple companies, with I think one exception and even that one wasn't as slow as people talk about, despite being the worst I ever encountered.

In fact, I'd argue that one of the biggest annoyances I had in last job was that I actually missed JIRA, or rather it's glorious issue list view with its keyboard shortcuts.