Leonid Shalupov
7480befe32
Using of Kotlin reflection for simple operations like bean management is very slow First time initialization time: 261 ms for `copyBean(K2JVMCompilerArguments())` Subsequent calls of `copyBean(K2JVMCompilerArguments())` take 1.7 ms per call Unfortunately compiler argument handling is also used in Kotlin IntelliJ plugin to parse facet settings. Big projects may have thousands of Kotlin facets The same `ArgumentUtilsKt.copyProperties` frame is seen across various freezes: IDEA-252440 2-3 minutes freeze on Kotlin project reimporting in last 203 eap IDEA-253107 A lot of short freezes (1-3 sec) during Kotlin project development KTIJ-23501 Make main run configuration detection lighter KTIJ-22435 Unresponsive UI with 100% cpu Reflection issue: KT-56358 KClasses.getMemberProperties takes too much time This commit replaces all reflection stuff with a simple code generation Now `K2JVMCompilerArguments().clone()` goes to hard-to-measure time
24 lines
1.0 KiB
XML
24 lines
1.0 KiB
XML
<component name="ProjectRunConfigurationManager">
|
|
<configuration default="false" name="Generate Compiler Arguments Copy" type="GradleRunConfiguration" factoryName="Gradle" folderName="Generators">
|
|
<ExternalSystemSettings>
|
|
<option name="executionName" />
|
|
<option name="externalProjectPath" value="$PROJECT_DIR$/generators" />
|
|
<option name="externalSystemIdString" value="GRADLE" />
|
|
<option name="scriptParameters" value="" />
|
|
<option name="taskDescriptions">
|
|
<list />
|
|
</option>
|
|
<option name="taskNames">
|
|
<list>
|
|
<option value="generateCompilerArgumentsCopy" />
|
|
</list>
|
|
</option>
|
|
<option name="vmOptions" />
|
|
</ExternalSystemSettings>
|
|
<ExternalSystemDebugServerProcess>true</ExternalSystemDebugServerProcess>
|
|
<ExternalSystemReattachDebugProcess>true</ExternalSystemReattachDebugProcess>
|
|
<DebugAllEnabled>false</DebugAllEnabled>
|
|
<ForceTestExec>false</ForceTestExec>
|
|
<method v="2" />
|
|
</configuration>
|
|
</component> |