Would like to see the prompt that generated this article because it's narrowly looking at underlying base framework performance as its only metric, yet buries that lede very well (at least in prose - obvious enough from the data of course).
Of course the conclusion is wrong though - looking at the data I would conclude that it's base framework performance that "doesn't matter" as a metric rather than framework choice itself.
Frameworks do matter in the sense that a good, well-organized, well-thought out framework will always outperform a shabby one. And the throughput matters. But having said that - it's a fine balance.
We moved one of our customers from a vanilla wordpress backend (gotta be the shittiest code organization I've ever seen) to a custom Phoenix/Elixir based backend that handles over 500M+ requests at 1/3rd the cost of competitors and 40% cheaper than their old Wordpress backend. So yeah, it really does affect the bottom line.
The problem with the OP article is that it’s a tiny toy:
> “Three tables: Publisher -> Author -> Book. Seeded with 4,215 real books from the Open Library API: Agatha Christie, Dostoevsky, Penguin Books, real data with real-world cardinality.”
What “real-world” application is that tiny? You could keep this all in RAM on a machine with say 16 MB or so of RAM (not GB!) A Raspberry Pi would be overkill.
The lesson from the article is, a framework doesn’t matter if your scale is below the mom-and-pop shop level.
I've always chosen frameworks for their abstractions and their design decisions, rarely their performance. Great research by the author, I feel better about that decision now.
I drew basically the opposite conclusion.
This article is slop. He made a tiny toy and drew an extreamly broad conclusion from it under very limited load.
If your load looks like this, then yeah, it does not matter, because a $40 android phone could run your server.
If your problem is mostly database bound then of course the database and ORM matter more than the HTTP loop.
Their framework selection did not really make sense either for a worst case for framework overhead. There are much slower python frameworks.
Would like to see the prompt that generated this article because it's narrowly looking at underlying base framework performance as its only metric, yet buries that lede very well (at least in prose - obvious enough from the data of course).
Of course the conclusion is wrong though - looking at the data I would conclude that it's base framework performance that "doesn't matter" as a metric rather than framework choice itself.
Frameworks do matter in the sense that a good, well-organized, well-thought out framework will always outperform a shabby one. And the throughput matters. But having said that - it's a fine balance.
We moved one of our customers from a vanilla wordpress backend (gotta be the shittiest code organization I've ever seen) to a custom Phoenix/Elixir based backend that handles over 500M+ requests at 1/3rd the cost of competitors and 40% cheaper than their old Wordpress backend. So yeah, it really does affect the bottom line.
The problem with the OP article is that it’s a tiny toy:
> “Three tables: Publisher -> Author -> Book. Seeded with 4,215 real books from the Open Library API: Agatha Christie, Dostoevsky, Penguin Books, real data with real-world cardinality.”
What “real-world” application is that tiny? You could keep this all in RAM on a machine with say 16 MB or so of RAM (not GB!) A Raspberry Pi would be overkill.
The lesson from the article is, a framework doesn’t matter if your scale is below the mom-and-pop shop level.
I've always chosen frameworks for their abstractions and their design decisions, rarely their performance. Great research by the author, I feel better about that decision now.
I drew basically the opposite conclusion. This article is slop. He made a tiny toy and drew an extreamly broad conclusion from it under very limited load. If your load looks like this, then yeah, it does not matter, because a $40 android phone could run your server. If your problem is mostly database bound then of course the database and ORM matter more than the HTTP loop.
Their framework selection did not really make sense either for a worst case for framework overhead. There are much slower python frameworks.
“ No database, no ORM, no serialization. Pure framework overhead.”
And many more examples. Great, another AI written article.
I feel dumb now. I already wrote a comment about this useless slop.