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
I also don’t think it’s a fair comparison. There’s nothing stopping me from loading the model into the memory of each Flask process (or some shmem), and getting the same performance or possibly better than the Postgres implementation, considering coroutines are being used in the Python case.

Calling this Postgres vs Flask is misleading at best. It’s more like “1 tier architecture vs 2 tier architecture”

>>pushed+4a
You get it. 1 tier is better than 2 tier. Python can't be 1 tier, unless it loads the full dataset which is not generally feasible for production online inference cases. PostgresML is 1 tier, and supports the traditional Python use cases.