You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, firstly, thanks @unlight and other contribs for this amazing GQL libs.
I am currently using the lib for a medium-sized project with about 60 tables, and concerned about further extending the codebase with many things relied on the library due to TypeScript / VSCode performance. Though understandable it is an upstream performance issue, but I think we could all share our tips and practices to develop awesome GQL API together with this lib.
Could we all share and discuss about our schema size, generator configs and rough performance
maybe in a format like, or discuss if any further profiling configuration is needed
emitSingle = true
emitCompiled = true
time to start Nest.js = 5m46s
time to generate Prisma = 43s
index.js 200k lines
index.d.ts 50k lines
emitSingle = true
emitCompiled = false
time to start Nest.js = 20s
time to generate Prisma = 16s
index.ts 120k lines
reExport = Single
emitSingle = false
emitCompiled = false
time to start Nest.js = 27s
time to generate Prisma = 17s
remark: will face many Excessive Stack Depth Comparison issues
reExport = Single
emitSingle = false
emitCompiled = true
time to start Nest.js = 55s
time to generate Prisma = 40s
Hi guys, firstly, thanks @unlight and other contribs for this amazing GQL libs.
I am currently using the lib for a medium-sized project with about 60 tables, and concerned about further extending the codebase with many things relied on the library due to TypeScript / VSCode performance. Though understandable it is an upstream performance issue, but I think we could all share our tips and practices to develop awesome GQL API together with this lib.
Could we all share and discuss about our schema size, generator configs and rough performance
maybe in a format like, or discuss if any further profiling configuration is needed
Related
#178
The text was updated successfully, but these errors were encountered: