Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decrease the amount of generated TS types (performance issues) #437

Closed
dankochetov opened this issue Apr 11, 2023 · 17 comments
Closed

Decrease the amount of generated TS types (performance issues) #437

dankochetov opened this issue Apr 11, 2023 · 17 comments
Labels
enhancement New feature or request

Comments

@dankochetov
Copy link
Contributor

dankochetov commented Apr 11, 2023

Based on Discord conversation https://discord.com/channels/1043890932593987624/1095436601426972822/1095436601426972822

@dankochetov dankochetov converted this from a draft issue Apr 11, 2023
@dankochetov dankochetov added the enhancement New feature or request label Apr 11, 2023
@pedropmedina
Copy link

I'm also experiencing this issue. It makes drizzle impossible to work with tPRC in a midsize project.

@arpadgabor
Copy link

I'd like to chime in here with the same issue - I'm working in a monorepo with drizzle and zod both (no trpc fyi), and with 7 schemas and ~88 total columns, intellisense takes up to 10s to load up (32gb ram, ryzen 9 5900hs). I think performance issues might be pretty important before the project (i.e. drizzle) gets too big 😅

@ngregrichardson
Copy link
Contributor

I've started to have these problems with just 20 tables, maybe 10-15 columns each.

@cayter
Copy link
Contributor

cayter commented May 23, 2023

Coming back to check on this again, is anyone using this library on production already? And do they have more than 20 tables? If yes, how do they workaround the slow intellisense issue? Would be really great if we can get some insights here. So far, I'm only seeing lots of YouTubers and tweets talking about how better drizzle is, but it seems all those are just doing a small demo showcase which isn't really practical. Thanks!

@cat-ninja
Copy link

Same here, I have ~85 tables and Intellisense is suuuper slow in VS Code.

@briangwaltney
Copy link

Same. 45 tables. Neovim running tsserver is quite painful.

I'm on hold moving my project until this dx is improved.

@hisamafahri
Copy link

+1 here. Experiencing same issue.

Only have about ~10 tables, and the intellisense is really-really slow.

@gabrielsch
Copy link

same here, 5~6 tables and already really slow, tried using the as string approach discused on Discord, but that breaks relations, I've removed it from some tables and then the performance was down again

@atanaskanchev
Copy link

+1 :: 25 tables/<15 columns in a monorepo, trpc, zod on m1 mbp/16gb: vscode struggles and the ts server often crashes

@ESchouten
Copy link

Update from the Drizzle team: Tweet
"We'll make it a priority on Jul"

@mdkq
Copy link

mdkq commented Jun 23, 2023

+1

@isaacfink
Copy link

How are people using drizzle with typescript running this slow? I keep seeing new projects and I feel like I am doing something wrong because in my experience drizzle is completely useless for a medium sized project

@ngregrichardson
Copy link
Contributor

ngregrichardson commented Jul 2, 2023

How are people using drizzle with typescript running this slow? I keep seeing new projects and I feel like I am doing something wrong because in my experience drizzle is completely useless for a medium sized project

My best luck has been with Webstorm with 8 or more gigs of ram. I have a project with about 15 tables, <15 cols each

@darkliyznyanlin910
Copy link

Same here. I'm working with 15+ tables with around 10 columns each and multiple relations. my intellisense and typescript server crashes frequently.

@masterbater
Copy link

I'd like to chime in here with the same issue - I'm working in a monorepo with drizzle and zod both (no trpc fyi), and with 7 schemas and ~88 total columns, intellisense takes up to 10s to load up (32gb ram, ryzen 9 5900hs). I think performance issues might be pretty important before the project (i.e. drizzle) gets too big 😅

bump it up to 128gb of ram

@seb-lewis
Copy link

Well I guess I will hold off on migrating to drizzle, fearing it will be a waste of time if I can't work on the project once implemented 🫤

@AndriiSherman
Copy link
Member

We've picked #800 issue to be a tracking issue, so will close this on favour of #800

@github-project-automation github-project-automation bot moved this from Backlog to Done in Public Roadmap Jul 23, 2023
@AndriiSherman AndriiSherman unpinned this issue Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests