3 ms·
Usually when people have speed problems with Jetbrains IDEs it's one of two things: 1. Heap size is too small and it's GCing a lot without the user realizing.
by native_samples 5y ago
Usually when people have speed problems with Jetbrains IDEs it's one of two things:
1. Heap size is too small and it's GCing a lot without the user realizing. Open IDE VM options and double the -Xmx setting.
2. Using a 4k display on macOS. Try the new JBR17+Metal builds. They aren't shipped yet but switch it to using Metal to render. Makes it a lot faster.
- Aeolun 5y agoHuh. Nr 2 is applicable to me. Will give it a try. Can’t see how it’ll fix my permanent indexing, but maybe it’ll at least feel faster. My heap size is already at 3GB, which I feel should be enough for opening a bunch of 5kb text files :/
- native_samples 5y agoIf you're permanently indexing something is very wrong and that will indeed break your IDE. That's just a bug. Try wiping all your caches from the menus and see if that helps. Otherwise file a bug in YouTrack.