[GROOVY-2065] GroovyScriptEngine loadScriptByName have a poor performance in Network drives

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.1-beta-1, 1.1-beta-2
• Fix Version/s: 1.7-rc-1
• Component/s: class generator
• Environment: Microsoft Windows XP professional, Java 1.5.0_11-b03
• Assignee: Jochen Theodorou
• Reporter: Vinícius Godoy de Mendonça
• Created: 16/Aug/07 10:03
• Updated: 12/Oct/09 18:26
• Resolved: 12/Oct/09 18:26

Description

1. Create a network drive, and map it to some letter;
2. Create a script folder in this network drive and write some scripts in it;
3. Make a GroovyScriptEngine named engine and loads those scripts by calling the loadScriptByName(scriptName, engine.getParentClassLoader()) command.

The load method will take something about 5-40 secs to parse the script file.
We also notice that this delay does not occur while using GroovyClassLoader.

I don't know if this information will be useful, but our network drive is in a Linux machine with Samba.

We do not tested using the run command, because such command is not useful to us.

Best regards,

Vinícius Godoy de Mendonça
Siemens Enterprise Communications