Bug #2716: very long Groovy compilation time when launching import modules for the first time in a session - Plateforme TXM - Forge du Centre Blaise Pascal

Bug #2716

very long Groovy compilation time when launching import modules for the first time in a session

Added by Matthieu Decorde almost 4 years ago. Updated over 2 years ago.

Status:

New

Start date:

01/16/2020

Priority:

Urgent

Due date:

Assignee:

% Done:

80%

Category:

Macros

Spent time:

Target version:

TXM 0.8.2

Description

Currently there is a very long compilation time before running any Groovy script (at first run or after editing a script).

Solution 0¶

The GroovyScriptEngine classloader needs to access all ClassLoaders to find out unknown classes (e.g a TXM extension classes like the "URSCorpora" class)

reduce the number of tested ClassLoader when the GroovyScriptEngine loads a class :

only use TXM plugin loaders -> ~ 70 loaders
only use the "*.rcp" plugin loaders (they contains the "*.core" plugin loaders) -> 34 loaders
~~test the EclipseClassLoader name against the loaded class package name~~
- first speed tests were not good

Related issues

Associated revisions

Revision 3004
Added by Matthieu Decorde almost 3 years ago

less ClassLoader to check when calling Groovy scripts refs #2716

History

#1 Updated by Matthieu Decorde about 3 years ago

Subject changed from RCP: X.X, pre-compile Groovy scripts to very long Groovy compilation time when launching import modules for the first time in a session
Description updated (diff)