Plugin adds huge overhead for projects imports in IntelliJ on Windows since 2.2.0

[ingokegel]

What happened?

The profiler shows that most time is spent creating ZIP file systems which is very slow on Windows compared to macOS and Linux and the plugin is responsible for all of them.

Could these file systems be cached?

Relevant log output or stack trace

Steps to reproduce

For example, with

https://github.com/ingokegel/jclasslib

if the org.jetbrains.intellij.platform version in idea.gradle.kts is set to 2.1.0, the time for the project import is ~20 seconds. With 2.4.0, it is ~50 seconds.

Gradle IntelliJ Plugin version

2.4.0

Gradle version

8.13

Operating System

Windows

Link to build, i.e. failing GitHub Action job

No response

[ingokegel]

Unfortunately, 2.5.0 does not improve the import times. Here is the call tree of the import:

The total import time is shown in the root (~ 90 seconds) and the IntelliJ Platform Gradle Plugin is responsible for a whopping 70% of that total time (classes other that com.jetbrains.* classes are filtered, and their time is added to the root node).

This is a fully warmed up situation, after repeating the import multiple times. The plugin does not perform any HTTP requests as verified by the profiler. Nearly all the time is spent creating nio file systems.

[hsz]

@ingokegel 2.5.0 was not aiming to improve that situation. The ball is now on the Plugin Verifier's side.

[ingokegel]

@hsz Thanks for the update! I didn't see the "depends on plugin verifier" label.