redhat-developer / redhat-developer/vscode-java

Tips for performance when opening big projects like Keycloak?

Open
#2,537 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Maven performance question
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

I'm working with Keycloak, which is a big code base.

Opening the project is quite frustrating: it takes 5+ minutes for the things to settle down. It seems that just closing and reopening vscode with the project open will take very long as well, at least if there are any changed files (like after small git pull).

I wonder if too much of the code base is compiled since the compilation also shows errors for modules that are not shown when compiling with maven on command line (which takes 2 minutes btw). Maybe the active maven profile is not obeyed? Keycloak code base might have some maven modules that are not maintained anymore and it would be desirable to include only the relevant ones.

I would appreciate any pointers on how to troubleshoot and optimize the performance of opening a big project such as Keycloak.

Thank you!

Environment
  • Operating System: Ubuntu 20.04.4 LTS
  • JDK version: OpenJDK Temurin-11.0.15+10
  • Visual Studio Code version: 1.68.1 (x86)
  • Java extension version: redhat.java@1.8.0
Steps To Reproduce
  1. git clone https://github.com/keycloak/keycloak
  2. open the project
Current Result
Expected Result
Additional Informations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Reproduce the report by cloning Keycloak on Ubuntu 20.04.4, opening it in VS Code 1.68.1 with redhat.java 1.8.0, and observing project initialization and compilation; investigate whether Maven profiles or unrelated modules are included. Done would be a documented cause and actionable optimization or configuration guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.