nplusone

While I have yet to work with a large Django monorepo, it's the architecture I'm leaning towards for a product I'm building. Are you guys using packages like nplusone [0] to help with some of this ORM complexity? As I mentioned, I am headed in this direction so I'm curious to hear your insight. I'd also love to pick your brain on any other pitfalls of this approach. [0] https://github.com/jmcarp/nplusone

Rails has Bullet[0] to help identify and warn you against N+1 Does Django have anything active? Quick search revealed nplusone[1] but its been dead since 2018. [0] https://github.com/flyerhzm/bullet [1] https://github.com/jmcarp/nplusone

I really appreciate your comment, I think I will add your log line idea to my project at work! I also wanted to disable lazy fetching of foreign keys, and I wrote something for it, then decided it was too risky to use in production (monkey patching) so I ended up just running nplusone [0] locally and fixed the issues it detected. Really would like Django to add this feature so it can be enforced properly though! [0] - https://github.com/jmcarp/nplusone

I’ve experienced a lot of n+1 queries problems as causes for bad performance. Often times this was a result of wrapping the ORM in abstraction layers (for business logic and fears of being “locked in” to the ORM). We rewrote that part of the application using a different ORM (in Python). Making use of a tool that could help find these problems automatically helped greatly and we didn’t have a single performance problem when we went into production the rewritten service. This module can detect the n+1 queries problem automatically in Python ORMs: https://github.com/jmcarp/nplusone Looking forward to seeing more automated tools like this in the Python/Django world.