convex dev server can take up to minute to update, what can I do?
hey all 👋 , my Convex dev server can take as long as a minute to reflect changes, which is a big hit to development speed. it seems that errors elsewhere in the code can also prevent the server from updating. For instance, if you attempt to reference an 'internalQuery' within an action, but there's a typo or mistake in the action code (like unclosed brackets), it results in errors and the dev server will not have updated
internalQuery. So I often find myself staring at the screen, waiting for the Convex dev server to update.
is there is anything I can do to make the convex dev server faster?
12 Replies
looking at the logs it seems that indexes might have something to do with this, but that is just guess on my part
What type of laptop are you on?
Also how many functions are in the file you’re updating?
my laptop is M1 Max. Also this seems to happen regardles of which convex file I'm working on. I usually try to put queries and mutations in separate files. currently the biggest file I have is a mutation file where I have 14 mutation there
also hi @Web Dev Cody 👋 good to see you here!
@fawwaz would you message me the name of your dev deployment?
would the dev deployment url, do ?
https://acrobatic-mule-913.convex.cloud
We have a project underway to address this. Is there a dependency you added today that might be large?
also curious about your internet connection speed — although we're going to improve this, those are the factors in play here in case you have control over them
hmm, could be after I added the clerk sdk?
for I work in different places some has better internet speed than others but haven't noticed this to be a factor
helpful to hear, we'll make a repro and include clerk in case that is one
@fawwaz have you tried
npx convex dev --typecheck=disable ? It might help a little bit.no didn't know this one exist will try this one today and will report back 👍
For what it’s worth, I had a similar issue a few weeks back - I’m now fairly certain it was due to bad Wi-Fi
Speed was fine, but the actual connection quality from the router was not
Hey @ballingt I think I have to revise my claim about internet speed is not a factor. After looking closely and testing today at three different places, I agree with @erquhart seems internet speed is a big factor!
