It should cache the intellisense information. It is recalculating it every single time you type, regardless of whether that library has changed at all.
It makes development an absolute pain, coupled with the glitchy intellisense menus which disappear randomly and re-appear (separate bug already posted, and still not fixed).
In this video you can see it’s even a problem with game:…
You can also see how glitchy and erratic the behavior of intellisense can be. I press enter but it just disappears, waits 2-3 seconds and then re-appears where enter finally works.
Expected behavior
Intellisense should be nearly instant and definitely cached where possible.
Intellisense dialog should not mysteriously disappear right when you press enter to select something and then magically re-appear again after a few seconds and finally allow you to press enter and have it work.
Yeah, I’ve also been noticing this happening to me as well. I was wondering if it was because of me having a large script. Personally, It doesn’t affect me that much, however it could definitely slow down programming.
Thank you for the bug report, do you have a place file that you’re willing to share to help us figure out what might be slowing down Autocomplete in this case?
We enabled some changes a few hours ago that should have improved the slowest scripts by 30% in a certain pet game, but if it caused a regression instead, we will disable it and re-evaluate.
This is still a major problem for us and has slowed our development down significantly. It is now taking up to 30 seconds on the latest Intel hardware (i9-13900k, 128gb ram, etc…). Any update on this? Really appreciate all of the hard work that is being put into Luau, and I know we are pushing it - but I believe that Luau is the future and we have adopted it wholeheartedly.
To paraphrase my update in the other thread: We believe we have fixed the bug which causes Autocomplete to fail-to-accept, but the general Autocomplete slowness is harder to fully fix. Autocomplete is ultimately powered by the Luau type system, so the longer the script takes to typecheck, the longer autocomplete results will take.
We do have some ideas for improving Autocomplete’s performance, and particularly providing a more user-friendly failure mechanism - which we are actively working on right now. But, without a repro case it is difficult to know if it will improve your particular place.
Following up, it is completely broken in the project we’re working on now. No autocomplete whatsoever. All we get are improperly formatted error lines, random red/orange bars streaming across our screens, etc. Screenshot below (my code has been stuck like this, in many different places)
Did this just happen today, or has it been going on for a while? What happens if you modify the script? If it’s consistent, can you send in a repro case by DM?
Started happening more recently. Intellisense / type-checking takes about 30 seconds on our project, and the type cache clears about every 15 seconds. We’ve reverted to basically just typing off of memory at this point. We’re really in need of getting Intellisense working again Thank you for all of the hard effort. Having this fixed means the world to all of us.
Our team is actively working on the problem; we’re seeing promising results (reduced cache invalidations, and improved performance with a cold cache) in your repro case and will keep you updated on our progress, but we do not yet have an ETA on all the changes.
Seems to be getting worse by the day It’s turned into notepad with syntax highlighting that takes about 30-6 seconds to load. Our library is taking about 60-120s to load intellisense/typechecking.
Hi @CoderJoey, sorry to hear that! We will have another fix in next release, which will allow typechecking runs in parallel. I just want to confirm whether you are still experiencing the syntax highlighting and performance slowdown issue that you mentioned in your previous post at this location: Intellise is EXTREMELY slow with larger code bases - #4 by CoderJoey? If that’s the case, I’d like to discuss this with our team to try and reproduce the issue from that place.
I’ve also been expieriencing a issue with random stuff getting underlined with no purpose. A day ago everything was fine with no edits the next day it happened. Although it doesn’t effect me that much it can be very confusing and irritating to deal with.
Any update on this? Is there anyway we could somehow analyze what types in our code is taking the longest so we can fix those things? We have tried going through our code piece of by piece to reduce type-checking complexity. It helped some, but it’s still basically just as slow. Taking around 30 seconds to load type information and apply type checking.
We have discovered that there are a few UI operations that can accidentally clear the typechecking cache, such as opening a new script in the editor or switching between 3D view tabs. We are currently working on a solution to address this issue. If you happen to come across a reliable way to trigger the clearing of the typechecking cache when it shouldn’t, please do let us know.
Thank you for all of the hard effort. Having this fixed means the world to all of us.