4:53 a.m.
are there are any benchmarks around number of rules that can be created in a
package in Guvnor?
we run Guvnor 5.3.0.final in Guvnor on a windows server that has 1.4 GB heap
and we are seeing memory issues when the package has reached around 900
rules or so.
by memory issues, I mean that after the package is built successfully,
memory is not being released back. this behaviour is more obvious at such
high number of rules in package than when we had just around 600 rules or
so.
also, when we try to load the package generated (around 6.4 MB) into the
knowledgesession, it crashes the system .
are there any recommendations on
1. whether we can split up a package into two separate packages, and load
the 2 of them separately one after the other into the session ?
2. amount of memory that guvnor needs to build such high number of rules ?
3. ways to shrink the number of rules as per some best practices while
still meeting requirements ?
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
1:04 p.m.
just wanted to ask one of the questions again.
currently, we have around 900 rule assets as shown in Guvnor. some of them
are decision tables which mean that the total number of rules might be lot
higher ( because each decision table on average has around 20 rows or so)
assuming that the number of rules comes to around 1500 or so,
can we
1. split this one package in Guvnor into 2 packages, build them separately
in Guvnor
2. and load each of them one after the other into the knowledgebase?
will this make any difference to the way memory is consumed during loading
the rules into the knowledge base?
currently, when loading the single package into the knowledgebase, our
windows server is crashing throwing OutOfMemory error.
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
5:16 p.m.
Hello,
On one of the drools project I worked before (end if 2011), we were using :
1) Guvnor as rule authoring and repository. Decision tables are updated
automatically from remote via the rest api => 100 000 rules in total
2) The package is built on guvnor => 64 bits JVM Heap of 6 GB and on a
virtual environment with 2 core and a standard server => 3-5 minutes to
build the package
3) the run time are loading the package in binary format => 30 seconds to
upload the binary and to build the knowledgebase
4) the project consists of calculating costs during all day, in batches, in
real-time, etc.. => 32 bits JVM and in 1.5G of heap, 3 threads are running
in parallele and building/removing statefull sessions.
We never came into memory issues but when you run a test scenario, it
builds the package so if there are one than one user autoring rules and
tests scenarios => Take memory. It i why we decided to go to a 64 bits JVM
to be able to have a bigger heap.
I hope it helps
Nicolas Héron
2012/2/6 vadlam [via Drools] <ml-node+s46999n3718794h47(a)n3.nabble.com>
just wanted to ask one of the questions again.
currently, we have around 900 rule assets as shown in Guvnor. some of them
are decision tables which mean that the total number of rules might be lot
higher ( because each decision table on average has around 20 rows or so)
assuming that the number of rules comes to around 1500 or so,
can we
1. split this one package in Guvnor into 2 packages, build them separately
in Guvnor
2. and load each of them one after the other into the knowledgebase?
will this make any difference to the way memory is consumed during loading
the rules into the knowledge base?
currently, when loading the single package into the knowledgebase, our
windows server is crashing throwing OutOfMemory error.
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
To unsubscribe from Drools, click
here<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=...
.
NAML<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=...
-----
Nicolas Héron
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
12:58 a.m.
Nicolas,
what is the size of the pkg file that gets loaded into your knowledge base?
when our pkg file was around 3 MB, we were able to load it successfuly into
a 1GB heap machine successfully
but when the package size grew to around 6.4 MB , we are no longer able to
load it into the 1 GB heap machine . it throws OOM errors.
we will soon be trying the loading on a 1.4 GB heap machine.
also, we noticed that when building the package in Guvnor on a 1.4 GB heap
machine windows 32 bit using Jrockit , around the time when it reaches 8%
heap , the physical memory is noticed to be consumed, but after the build is
complete , the heap memory is not released back . it stays at 85% . also the
physical memory is not released back.
I wonder if this has anything to do how Guvnor saves the package built or
any other references it has to objects being left in memory ?
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
1:08 a.m.
Hi,
Remember that the memory is only released when java needs some space in the
heap (GC).
On the size, I do not know but more than 10 MB for sure as it takes 2 to 6s
to transport it over the network and it is a 100MB network.
I first started the project on a 32 JVM and always came into memory trouble.
And It was a problem as the customer only had 32 bits JVM which may be your
case also !
I had to convince him and on 2000 Jboss server, Guvnor is the only one in
64 bits JVM !
There may be also a memory leak.
Do you have an official support from Jboss/Redhat ? In your case they shall
help you as they will take time to test your case. If not, I am sorry but
at the end your only realistic solution => 64 bits JVM
cheers
Nicolas
2012/2/6 vadlam <sreeram.vadlamudi(a)wellsfargo.com>
Nicolas,
what is the size of the pkg file that gets loaded into your knowledge base?
when our pkg file was around 3 MB, we were able to load it successfuly into
a 1GB heap machine successfully
but when the package size grew to around 6.4 MB , we are no longer able to
load it into the 1 GB heap machine . it throws OOM errors.
we will soon be trying the loading on a 1.4 GB heap machine.
also, we noticed that when building the package in Guvnor on a 1.4 GB heap
machine windows 32 bit using Jrockit , around the time when it reaches 8%
heap , the physical memory is noticed to be consumed, but after the build
is
complete , the heap memory is not released back . it stays at 85% . also
the
physical memory is not released back.
I wonder if this has anything to do how Guvnor saves the package built or
any other references it has to objects being left in memory ?
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
8:15 a.m.
Nicolas,
after we run a build and we see that the heap has not been Garbage
collected, when we try run a second build, it crashes after a few minutes
because it does not have much memory to complete the build.
could it be the case that the package that gets built is getting stored and
not released unless the server is restarted?
what is the expectation around a package that has been built in Guvnor.
How long is it retained in Guvnor memory for subsequent access through a
URL?
The same rules get built in Guvnor 5.2 and memory is subsequently released
after the build.
so, it looks like there is some kind of leak happening ?
to contest my own theory, when a package which is smaller in size is built
in Guvnor 5.3, memory is released after the build.
I wonder what could be happening around that 80-85 heap threshold that is
causing memory to be held back.
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
4:55 a.m.
IIRC there was a bug in Drools Expert 5.3 that was not releasing event
listeners correctly that led to a memory leak - it might be related to what
you have experienced. IIRC this was fixed for 5.4.
Are you able to try with Drools suite 5.4.0.beta2?
sent on the move
On 7 Feb 2012 23:16, "vadlam" <sreeram.vadlamudi(a)wellsfargo.com> wrote:
Nicolas,
after we run a build and we see that the heap has not been Garbage
collected, when we try run a second build, it crashes after a few minutes
because it does not have much memory to complete the build.
could it be the case that the package that gets built is getting stored and
not released unless the server is restarted?
what is the expectation around a package that has been built in Guvnor.
How long is it retained in Guvnor memory for subsequent access through a
URL?
The same rules get built in Guvnor 5.2 and memory is subsequently released
after the build.
so, it looks like there is some kind of leak happening ?
to contest my own theory, when a package which is smaller in size is built
in Guvnor 5.3, memory is released after the build.
I wonder what could be happening around that 80-85 heap threshold that is
causing memory to be held back.
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
3:49 a.m.
We also ran into similar memory issues. Some object references are not being
released. We load around 10,000 rules from different excels. When we reload
for the 2nd time (without server/JVM restart) heap size was almost increased
by 50%. It kept on increasing for each load and finally throws Out of memory
error.
I believe our issue is related to the following
https://issues.jboss.org/browse/JBRULES-2782
My previous posting related to our issue:
http://drools.46999.n3.nabble.com/org-drools-reteoo-ReteooRuleBase-not-ge...
--
View this message in context:
http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
4450
days inactive
4477
days old
7 comments
4 participants
participants (4)
-
dkrishna -
Michael Anstis -
Nicolas Héron -
vadlam