5:31 p.m.
Hi all,
i have read the Documentation and the Drools book. I am developping an
application but i don't understand in my case how i can loading a
1,000,000,000 facts (approx).
At present I load all facts into a StatefulKnowledgeSession with a for-
cycle and I insert them into ksession ("ksession.insert(customer);")
The problem is the out of memory exception due the high memory
requirements of facts.
How i can resolve it? There is another approach to
facts loading into session? Can i integrate the loading with JPA/Hibernate
frameworks?
Thanks in advance for any suggestion,
David
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Loading-facts-and-mem...
Sent from the Drools - User mailing list archive at Nabble.com.
5:52 p.m.
That seems a lot of facts, are you sure you really need that many facts in your knowledge
session?
What are you actually trying to achieve? Do you really need all of the facts in memory at
once?
Ignoring drools are you actually able to load them up into your JVM at all?
Thomas
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-
bounces(a)lists.jboss.org] On Behalf Of bellios
Sent: 08 September 2010 16:31
To: rules-users(a)lists.jboss.org
Subject: [rules-users] Loading facts and memory size limits
Hi all,
i have read the Documentation and the Drools book. I am developping an
application but i don't understand in my case how i can loading a
1,000,000,000 facts (approx).
At present I load all facts into a StatefulKnowledgeSession with a for-
cycle and I insert them into ksession ("ksession.insert(customer);")
The problem is the out of memory exception due the high memory
requirements of facts.
How i can resolve it? There is another approach to
facts loading into session? Can i integrate the loading with JPA/Hibernate
frameworks?
Thanks in advance for any suggestion,
David
--
View this message in context: http://drools-java-rules-
engine.46999.n3.nabble.com/Loading-facts-and-memory-size-limits-
tp1440236p1440236.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received
this message in error, please immediately notify the postmaster(a)nds.com and delete it from
your system as well as any copies. The content of e-mails as well as traffic data may be
monitored by NDS for employment and security purposes. To protect the environment please
do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United
Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603
8808 40-00
**************************************************************************************
11:23 p.m.
I assume you need all 1 billion facts in WM at once?
i.e. event processing\CEP\streaming isn't more suitable?
On 8 September 2010 16:31, bellios <carfid(a)gmail.com> wrote:
Hi all,
i have read the Documentation and the Drools book. I am developping an
application but i don't understand in my case how i can loading a
1,000,000,000 facts (approx).
At present I load all facts into a StatefulKnowledgeSession with a for-
cycle and I insert them into ksession ("ksession.insert(customer);")
The problem is the out of memory exception due the high memory
requirements of facts.
How i can resolve it? There is another approach to
facts loading into session? Can i integrate the loading with JPA/Hibernate
frameworks?
Thanks in advance for any suggestion,
David
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Loading-facts-and-mem...
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
10:27 a.m.
In my application I would to model the Customers-Sales domain and I thought
that drools could help me to express a set of rules to capture (or execute
on-demand) some "special" customers (e.g. take the customers which not
have/have bought some products of category X in the last 6 months).
To do this i'm loading the last 6 months sales into WM, afterwards on demand
i execute the rules. This process fails due the memory requirements. I
thought that Drools would use an hibernate/JPA/ or an incremental
mechanisms to load and process the facts.
@Swindells, Thomas: Do you think that it's the right approach?
@Michael Anstis-2: I will try to study in deep the event
processing\CEP\streaming methods.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Loading-facts-and-mem...
Sent from the Drools - User mailing list archive at Nabble.com.
10:45 a.m.
The easiest way to view drools is as an in memory relational database.
Rules are a type of efficient triggers that as soon as data changes causes actions to
occur in nearly real time. (Sorry for making people cringe with this overly simplified
explanation).
The use case you gave sounds like you are trying to perform a scheduled task which every
so often queries a database to select a category of people to perform some actions on.
This is most likely to be most efficiently done by just doing a sql query to get the
relevant data and processing it in the traditional way, though you may want to use Flow to
manage the perfoming and defining of the actions. Of course if your use case is actually
more complicated than this then you may want either a hybrid approach (a simplified sql
query to produce a superset of who will be effected and then more complex rules to pick
out individual customers with more specific criteria), or CEP approach may work - although
you will need to be careful that your CEP rules don't have the effect of keeping all 6
months worth of data in memory.
Thomas
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-
bounces(a)lists.jboss.org] On Behalf Of bellios
Sent: 09 September 2010 09:28
To: rules-users(a)lists.jboss.org
Subject: Re: [rules-users] Loading facts and memory size limits
In my application I would to model the Customers-Sales domain and I thought
that drools could help me to express a set of rules to capture (or execute
on-demand) some "special" customers (e.g. take the customers which not
have/have bought some products of category X in the last 6 months).
To do this i'm loading the last 6 months sales into WM, afterwards on demand
i execute the rules. This process fails due the memory requirements. I
thought that Drools would use an hibernate/JPA/ or an incremental
mechanisms to load and process the facts.
@Swindells, Thomas: Do you think that it's the right approach?
@Michael Anstis-2: I will try to study in deep the event
processing\CEP\streaming methods.
--
View this message in context: http://drools-java-rules-
engine.46999.n3.nabble.com/Loading-facts-and-memory-size-limits-
tp1440236p1444747.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received
this message in error, please immediately notify the postmaster(a)nds.com and delete it from
your system as well as any copies. The content of e-mails as well as traffic data may be
monitored by NDS for employment and security purposes. To protect the environment please
do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United
Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603
8808 40-00
**************************************************************************************
4:16 p.m.
It seems to me that you are planning the proverbial search for needles in a
haystack.
A better approach should be possible by monitoring the harvest while it
arrives,
one day at a time. (If you have to dig through the past, you still can do it
day
by day.) Use rules to keep track of sales events that qualify/disqualify
customers.
This should reduce the number of facts to a manageable order of magnitude,
i.e.,
the number of customers.
-W
On 9 September 2010 10:27, bellios <carfid(a)gmail.com> wrote:
In my application I would to model the Customers-Sales domain and I thought
that drools could help me to express a set of rules to capture (or execute
on-demand) some "special" customers (e.g. take the customers which not
have/have bought some products of category X in the last 6 months).
To do this i'm loading the last 6 months sales into WM, afterwards on
demand
i execute the rules. This process fails due the memory requirements. I
thought that Drools would use an hibernate/JPA/ or an incremental
mechanisms to load and process the facts.
@Swindells, Thomas: Do you think that it's the right approach?
@Michael Anstis-2: I will try to study in deep the event
processing\CEP\streaming methods.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Loading-facts-and-mem...
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
5044
days inactive
5045
days old
5 comments
4 participants
participants (4)
-
bellios -
Michael Anstis -
Swindells, Thomas -
Wolfgang Laun