Investigate Rexster Script-Engine performance issue.

[vantonio]

_This will NOT hit you if you are not using https://github.com/tinkerpop/rexster!_

I'm getting 200-2000ms to eval a single "g.addV" command, which is a nightmare comparing to Groovy's ~10ms.

A few things tried:
a) manually getting the binding script, combined it with the user script and interpret the whole in one interpret() call. This should have speed things up a lot but there's hardly a way to know since the interpreting time is so unstable and unpredictable;
b) tried to use the more light-weighted scala.tools.reflect.ToolBox, it should be faster but due a bug* in the toolbox compiler, we can't even import the tinkperpop libs properly :-(

Any thoughts?

*https://issues.scala-lang.org/browse/SI-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel

[vantonio]

Also scala 2.11 will have native support for jsr223 but it won't be ready until 2014, waiting is wasting:-(

[mpollmeier]

Thanks for all your thoughts, but I'm not sure if we can really speed it up at the moment. There's heaps to do in the core usability of gremlin-scala, so I'll focus on that instead.
That being said, if you do come across a better solution, let me know (here). I'll leave this issue open for now.

[vantonio]

Alexandre,

just making sure, i've updated the title to avoid future misunderstandings.

Regards,
Antonio

[mpollmeier]

Antonio is right, this is only for ad-hoc queries which you should only use for playing around and getting used to Gremlin.
I personally don't even do that but rather write compiled code that gets executed - either from a test case or Rexster.

HTH?