Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
8000 points to monit
-
your env.properities configuration is wrong,if you want to convert derby to mysql,configuration is like:
first creat one empty database in mysql,
then.
(new datase)
db.type=mysql
db.url=jdbc:mysql://localhost/samedb
db.username=
db.password=
db.pool.maxActive=10
db.pool.maxIdle=10
db.update.log.dir=${catalina.base}/logs/(old database)
convert.db.type=derby
convert.db.url=~/../../bin/mangoDB2
convert.db.username=
convert.db.password=grove.url=http://mango.serotoninsoftware.com/servlet
-
@hussam said:
your env.properities configuration is wrong,if you want to convert derby to mysql,configuration is like:
first creat one empty database in mysql,
then.
(new datase)
db.type=mysql
db.url=jdbc:mysql://localhost/samedb
db.username=
db.password=
db.pool.maxActive=10
db.pool.maxIdle=10
db.update.log.dir=${catalina.base}/logs/(old database)
convert.db.type=derby
convert.db.url=~/../../bin/mangoDB2
convert.db.username=
convert.db.password=grove.url=http://mango.serotoninsoftware.com/servlet
Thank you very much for your response!
And did you tried to increase values of parametres:
db.pool.maxActive=10
db.pool.maxIdle=10
without loosing stability?
If yes, did it cause improvement of Mango performance ? -
I suspect the database conversion will help a lot, and thanks for answering, hussam.
In regards to the second part of the first post, you could investigate tuning the -X arguments passed to the JVM in your .bat or .sh start up script, such as your -Xms (Initial heap). I don't know that you're going to need to go into situations where Mango will require more than 4Gb with 8000pnts/2minutes, although this of course depends upon the configuration and use case.
-
Thank you for your answer - phildunlap. According your advice - I also improved Java parameters -> following this tutorial: http://www.wikihow.com/Increase-Java-Memory-in-Windows-7. There is also option to set JAVA heap space in TomCat service, but despite all this actions, I still had JAVA cheap space after some time (even If I set 4GB).
But I guess that should be set inside Mango to make it work, because It will be overwrite by constans inside Mango? Am I wrong?
@phildunlap said:
I suspect the database conversion will help a lot, and thanks for answering, hussam.
In regards to the second part of the first post, you could investigate tuning the -X arguments passed to the JVM in your .bat or .sh start up script, such as your -Xms (Initial heap). I don't know that you're going to need to go into situations where Mango will require more than 4Gb with 8000pnts/2minutes, although this of course depends upon the configuration and use case.
-
**phildunlap ** I have additional question :) .
I was able to run Mango on MySQL but time from hitting Apache *startup * till the moment Mango starts, increased from couple of seconds to the 4 hours (database has 4.5GB)....
Is it possible to fix it? I use Apache 7.0.@phildunlap said:
I suspect the database conversion will help a lot, and thanks for answering, hussam.
In regards to the second part of the first post, you could investigate tuning the -X arguments passed to the JVM in your .bat or .sh start up script, such as your -Xms (Initial heap). I don't know that you're going to need to go into situations where Mango will require more than 4Gb with 8000pnts/2minutes, although this of course depends upon the configuration and use case.
-
A good thing to know is that you can put a file in your Mango root directory called "SAFE" and boot Mango with your datasources disabled. I suspect something in your configuration is causing an unnecessary delay, or your network is significantly slower than you're querying it. You could do some trial and error datasource/datapoint enabling.... or, have you investigated your mango/logs/ma.log? If so, swap debug-log4j.xml with log4j.xml in mango/classes for a boot, and let's have a look
-
Something to know is that in a very near release of the Mango Automation Enterprise license we will offer a NoSQL database option that gives impressive performance for very large systems.
-
Thank you very much for so prompt response! You have no idea how I appreciate it!
mango.log doesn't show anything special - without error/warnings but still freezed on startup level... ( maybe it is just me being impatient.... :oops: )
I decreased size of my database to the 1.2GB and problem is solved but question is how to avoid this kind of behavior - becouse in the future I will have - for sure huge database.Thank you for advice with disabling all of the sources - I guess it could possibly help. I I will find solution I will share with you :-).
@phildunlap said:
A good thing to know is that you can put a file in your Mango root directory called "SAFE" and boot Mango with your datasources disabled. I suspect something in your configuration is causing an unnecessary delay, or your network is significantly slower than you're querying it. You could do some trial and error datasource/datapoint enabling.... or, have you investigated your mango/logs/ma.log? If so, swap debug-log4j.xml with log4j.xml in mango/classes for a boot, and let's have a look
-
I can't wait Joel :D !
@JoelHaggar said:
Something to know is that in a very near release of the Mango Automation Enterprise license we will offer a NoSQL database option that gives impressive performance for very large systems.
