Hi,
We setup some Clover Graphs years ago that used to run on Java5 JRE, using command line.
The server has been upgraded to Java7 JRE, and the graphs execution now takes 4 times the usual delay (from 1,5hrs to 6hrs now).
Any idea how should I handle this ?
Should I add some parameter to the Java command line ?
Or should I add/change some configuration properties ?
Thanks for you help on this
Françoise
We setup some Clover Graphs years ago that used to run on Java5 JRE, using command line.
The server has been upgraded to Java7 JRE, and the graphs execution now takes 4 times the usual delay (from 1,5hrs to 6hrs now).
Any idea how should I handle this ?
Should I add some parameter to the Java command line ?
Or should I add/change some configuration properties ?
Thanks for you help on this
Françoise
-
Hi François,
That is quite strange behavior, however, I would like to kindly ask you to provide me with a bit more detailed information, so that I can better understand your setup, please.
- 1. What version of CloverETL software are you using?
2. Do you use CloverETL Server to run your graphs?
3. Do you use CloverETL Designer to create the graphs and then run them via command line tools?
4. Any other information you may consider important in this matter.
Thank you in advance, -
Hi,
Thanks for answering.
Here are some more details
1. CloverETL engine version 2.5.4
2. Not sure what you call Clover Server ? We have designed the graphs using Clover Designer (plugin within Eclipse), then we take the generated graph files (.grf), put this on the linux server and run command line like this :java -Xms512m -Xmx6144m
-cp ${CLOVER_HOME}"/lib/cloveretl.engine.jar":$COMMONS_LOGGING_JAR:$JAVOLUTION_JAR:$JMS_JAR:$JXL_JAR:$LOG4J_JAR:$POI_JAR:$TOOLS_JAR:$JANINO_JAR
-Djava.util.Arrays.useLegacyMergeSort=true
-Dclover.home=$CLOVER_HOME org.jetel.main.runGraph
-plugins ${CLOVER_HOME}"/plugins"
-P:PROJECT_DIR=$PROJECT_LOCATION
-P:FILES_DIR=$FILES_LOCATION
-cfg ${PROJECT_LOCATION}"/workspaceGraphes.prm"
-config ${PROJECT_LOCATION}"/defaultProperties"
${PROJECT_LOCATION}"/graph/updateV4-part1.grf"
3. Yes
4. Running the graph on the Java5 version within 1,5 hr was considered as correct performance as files treated are very large (973Mb in total) ; and this is running fine since years (almost 10 year) on the Java5 environment.
Any optimisation idea within Java7 is welcome.
Françoise -
Hi François,
Unfortunately, this is very old version of CloverETL software which is no longer supported. Version 2.5.x wasn't tested with Java 7 as it wasn't released at that time, therefore, we cannot guarantee full compatibility. I would suggest to upgrade to one of the recent versions of CloverETL software and test your graphs and Java 7 or 8 performance with your graphs there.
Best regards,
Please sign in to leave a comment.
Comments 3