Drools Workbench 6.2 and 6.3 slow on Docker

[Jeffrey Williams]

I'm running the drools workbench showcase docker image on a machine with 2 cores and 8 gig of memory (It is an EC2 m4.large)

with java options of -XX:MaxPermSize=512m -Xms1024m -Xmx2048m on Wildfly 8. 

There is a long loading time of 15-20 seconds whenver I navigate inside the project view folder tree or click on rule files (such as Guided Rules with DSL). I want to know if this is normal and if is not, then what can I do to speed it up.

Things I've done: I've tried increasing the java options up to -XX:MaxPermSize=512m -Xms2048m -Xmx3072m and upgrading to wildfly 9 (And in the process setting the java options to -Xms2048m -Xmx3072m). 

I have not been able to access the wildfly admin console and I've read the documentation and I am still trying to work that out. I find the drools workbench is excellent for what we're trying to do and if I can speed it up it will save me a lot of trouble.

I am not anchored to using docker for the workbench. The reason I would like to use it if possible is that I am already able to launch a new environment with it without any problems. If I have to look for alternate ways to use the drools workbench without docker, then that is fine as long as I get the speed gains I'm looking for.

[Michael Anstis]

Is this whenever you navigate to anything in the same project; or when switching between projects?

Drools Workbench distributions for Wildfly and EAP work out of the box; only add a user or two and off you go. Tomcat is more involved.

It'd be good for you to give it a go so we can be sure what you report is environmental.

--
You received this message because you are subscribed to the Google Groups "Drools Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-setup...@googlegroups.com.
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/8cb9cf2c-1d64-4c35-ab32-c62233eb6d90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeffrey Williams]

So this is happening for both the same project; or when switching between projects.

Not sure what you are asking us to try? Clean install of both of these without Docker?

We are running the Docker contain provided from official site and are seeing these issues. Would Docker not provide a consistent environment to test with?

--
You received this message because you are subscribed to a topic in the Google Groups "Drools Setup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/drools-setup/s5MEp1c2Jh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to drools-setup...@googlegroups.com.

To post to this group, send email to drools...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/CAAG9P0s_odqOfN7XUMZo8nNQwifbVqKsHZmmrc2uRF4%3DgFN%3D%3Dw%40mail.gmail.com.

[Michael Anstis]

If it happens within the same project it's most certainly unexpected. If it happens when navigating between projects it's expected on *large* projects - we perform a build when switching projects to populate the Messages console (it's to be refactored in the near future).

I was requesting you try with a standalone Wildfly/EAP installation as the behaviour you report is unexpected. It'd help rule out a variable - but you're correct in that we'd expect Docker images and standalone to be comparable if not identical.

To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/CA%2BO8zBOphmvhawFmdMGBtHrFT8OJ2ZzUksEcsn29c%3Dp2smAZ3g%40mail.gmail.com.

[Jeffrey Williams]

So this is happening for both the same project; or when switching between projects.

Not sure what you are asking us to try? Clean install of both of these without Docker?

We are running the Docker contain provided from official site and are seeing these issues. Would Docker not provide a consistent environment to test with?

[Roger Martinez]

Hey Jeffrey!

Did you try to check at the container's logs?? Probably there exist some exceptions and they can be the cause why it's slow or sometimes doesn't work.... 

I say that because you're deploying the containers on an EC2, and these docker community images are not intended for cloud environments such as OpenShift or EC2 - these environments has some restrictions that are not met in the images, as they can be different for each one, etc etc. You should use the drools-workbench image (not the showcase one) as base for your custom one, applying on it the considerations for your cloud environment.

Please let me know your findings :)

Thx!

[Jeffrey Williams]

Thanks guys we will attempt to install it stand alone and see if we can figure it out.

[Jeffrey Williams]

Thank you all for your advice.

We stood up a an instance in EC2 with wildfly and Drools 6.3 and everything is now fast and usable. We are looking to create s Chef script so we can automate the deployment through AWS opsworks.

Installing wildfly as a service we had to make a few changes to the wildfly-init-redhat.sh for those that are interested.

add

if [ -z "$JBOSS_USER" ]; then

JBOSS_USER=root

fi

[Mauricio Salatino]

So Jeffrey, did you abort the docker path? 

To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/4f1b8c1f-57c2-40bd-8608-e7db39bb08c6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

 - MyJourney @ http://salaboy.com

 - Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -