[ 
https://issues.apache.org/jira/browse/OFBIZ-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272862#comment-13272862
 ] 

Adam Heath commented on OFBIZ-4870:
-----------------------------------

There is multi-threading per-datasource during startup.  Multiple threads 
creating the tables/keys/etc.  Seed data(from xml) is still single-threaded.

I have a series of changes to fix this locally, but it's *really* complex.  
Since an xml import may already be part of an *existing* transaction, I 
absolutely *must* manipulate the database in the current thread.  The parsing, 
however, can be done in a background thread, in parallel.  Unfortunately, the 
xml parser in use is event based, in the wrong direction(push instead of pull), 
so the bulk of the change is flipping that around.  Tbh, the complexity wasn't 
really worth the speedup(just a few percentage points, afaicr).

What threaded stuff are you still seeking?
                
> Multithreading in GenericDAO / Delegator
> ----------------------------------------
>
>                 Key: OFBIZ-4870
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4870
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Mirko Vogelsmeier
>
> Hey there,
> some time ago there were some commits of Adam that brought in first ideas of 
> multi threaded delegator useage (r1139700).
> Depending on how intense the data useage or data size is, there are 
> performance issues we cannot scale by pure hardware and/or configuration as 
> there is just one Delegator object per datasource.
> I wanted to check on the progress of this very helpfull feature. Are there 
> any further thoughts to work on this?
> Greetings,
> Mirko

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to