zlacker

>>redbel+(OP)

  "In Python, most of the bottleneck comes from having to fetch and deserialize Redis data."

This isn't a fair comparison. Of freaking course postgres would be faster if it's not reaching out to another service.

>>chaps+b5
Yes, that's essentially the point being made here. It's a fair comparison if your intent is to run this kind of job as quickly as possible.

>>redhal+c7
No it's not. It tells me exactly nothing useful about the postgresml performance because it's impossible for me to rule out redis and the http server when factoring in performance. It's two hops, with a guaranteed delay that the postgres setup won't have.

If they wanted it to be a fair comparison they should have used FDWs to connect to the same redis and http server that the python benchmarks tested against.

>>chaps+P7
The article very clearly was pointing out that the performance advantage of postgresml comes from the architecture. Hell, they are even using the same exact algorithm. What benefit is to be had from benchmarking the same algorithm on the same architecture? Do we also need to make sure Teslas have internal combustion engines when we compare their performance to ICE cars?