For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 19 replies, 9 voices, and was last updated 20 years, 7 months ago by
.
-
Posts
-
In a JSP, whenever I do ctrl-space to get content assist, it takes a very long time. I’ve never gotten this before, ever. I’ve been using MyEclipse and Eclipse for the past 1.5 yrs. It’s making coding JSP’s extremely frustrating. This does not happen in regular java classes.
System Setup ——————————-
Operating System and version: windows 2003 Enterprise SP1
Machine: 3.6GHz P4, 4GB RAM, hyper threading=on, it’s fairly speedy
Eclipse version: 3.1.0
Eclipse build id: I20050627-1435
Fresh Eclipse install (y/n): yes
MyEclipse version: 4.0 M2
Eclipse JDK version: 1.4.2_08
Application Server JDK version: 1.4.2_08
Are there any exceptions in the Eclipse log file?
– Message Body ——————————-Trim down the number of JARs in your classpath, if you have many JARs, every time you invoke autocomplete it’s querying the index of all those 1000s upon 1000s of classes. If you can trim down your libraries to just compile-time dependencies, that will help speed things up.
Andy,
In the past, these have been the common issues for slow performance of auto complete:
This is almost always caused by having the workspace (and subsequently the library path) on a network drive
or some remote location instead of the local machine.
https://www.genuitec.com/forums/topic/building-workspace-slow/#post-234233Problem: Autocomplete is so slow to popup!
Solution: In 3 separate threads, each one was caused by the users having 50+ JARs in their build path, once the build path was trimmed
down to just compile-time required JARs, autocomplete was instant again.
