Hello, i'm just playing around with prisma and therefore

createMany

and was wondering if we might see the improvements proposed in https://github.com/prisma/prisma/issues/5437#issuecomment-772692381 are being considered to be pulled into the experimental mode? &/or as long as we don't how are you guys working around that issue 🤔 I got a cronjob batch upserting 50k docs and doing this sequentially seems like a rather bad idea - especially as i'm on serverless with function timeout-limits. I've now chunked it and process it with multiple lambdas, but that's a quite connection heavy approach. Is $rawQuery the way to go?

@sakulstra 👋 Yes currently

$queryRaw

would be the best way to do this.

Are perf optimizations on the short term roadmap though?/is there a public roadmap somewhere? Coming from mongoose, prisma is great in regards to typing and so on - i really enjoyed using it. In a test migration of a small side project things are very noticeable slower and while part of that might be mongodb vs pg I guess a big chunk is also coming from issues like: https://github.com/prisma/prisma/issues/5043 https://github.com/prisma/prisma/issues/5919 https://github.com/prisma/prisma/issues/5437 https://github.com/prisma/prisma/issues/4921 and so on which makes prisma a conflicted choice (as at the end for most things you have to opt out prisma via rawQuery).

Yes we do have performance in mind and here’s the official roadmap. Currently we are planning to add the features that are present in the roadmap and as for performance, once N-API support has been implemented, there will be a lot of implicit perf gains.

ah cool, thx for the link ❤️