3 ms·
Can you expand on your logic here? Is this because Python ORMs have gotten too bloated?
by jamestimmins 8y ago
Can you expand on your logic here? Is this because Python ORMs have gotten too bloated?
- friedman23 8y agoThey are bloated and they are not performant. If you are using Node and the main benefit of node is its asynchronous execution flow you would be shooting yourself in the foot by using an ORM and gaining all the overhead that comes from serialization and deserialization.
- zepolen 8y agoYour comment reeks of inexperience.
- friedman23 8y agoHaha, your comment reeks of inexperience. The thing you have namely not experienced is the pain of having to port an entire service to a different language because SQLAlchemy is as slow as a snail. But yes, keep on using your ORMs because using a query builder is too hard. I'm sure your significant experience building services that will at most ever handle 2 QPS is very important to the software engineering world.
- alter_eco123 8y agoFor what it's worth, if SQLAlchemy (or any other ORM) is slow, it's probably not because of "serialization" and "deserialization" (of whatever you had in mind), but because the database is queried in a (really, really) inefficient way. It's also unclear how that's related to whether you're working in an async environment or not. He was probably thinking about stuff like that.
- friedman23 8y agoOne of the biggest bottlenecks for us was creating these massive nested Python objects.
- zepolen 8y agoSo you ported an entire app to a new language instead of convert the hot paths to sqlalchemy's sql expression or even just optimized raw sql with bind params. Hope you learnt from that experience. You're still using a Query builder? Heh, maybe one day you'll learn how to write plain sql yourself. Also, I'm working in the 2,000TPS range. So don't bother.