When 2.1.0 came out the web page said, "New release of CloverETL - 2.1.0 - it brings major feature enhancements and speed improvement"
however when I run my 2.0.4 graphs in 2.1.0 (with necessary code changes) I found that they run slower overall. In 2.0.4 when I tell the graph to run it starts immediately but when I run a graph in 2.1.0 I get a bunch of
DEBUG [main] - Plugin org.jetel.component loaded.
id - org.jetel.component
version - 2.1.0
provider-name - null
and then nothing happens for 5 to 10 seconds before it continues. Since I am running several graphs in a row this delay really adds up, is there something I can do to get rid of it. I am building and running my graphs in a Java app.
however when I run my 2.0.4 graphs in 2.1.0 (with necessary code changes) I found that they run slower overall. In 2.0.4 when I tell the graph to run it starts immediately but when I run a graph in 2.1.0 I get a bunch of
DEBUG [main] - Plugin org.jetel.component loaded.
id - org.jetel.component
version - 2.1.0
provider-name - null
and then nothing happens for 5 to 10 seconds before it continues. Since I am running several graphs in a row this delay really adds up, is there something I can do to get rid of it. I am building and running my graphs in a Java app.
-
Hello Nathan,
can you tell me where exactly this delay happen (between which log message)? If last message is "Checking graph configuration..." you can try to turn off this checking by comment these lines of code in runGraph class:
//ConfigurationStatus status = graph.checkConfig(null);
//status.log();
It is probably that some of graph element waits there for some timeout on database connection or something like that.
Martin
Please sign in to leave a comment.
Comments 1