kukeltje: anonymous wrote : - Would be great if you could elaborate a little on the way creating the indexes impacted performance more than just the delete (thankfully it was not the coroner you had to call ;-))
(1) When we start up the jBPM java app, we load information about all the running instances from JBPM into our application. This is much faster after indexing the table (generally anything that gathers components of a process instance or process definition is significantly faster). (2) Eliminated (almost) deadlocks on tables by enabling row locking (3) No downgrade in run-time performance (process instances do not run slower due to overhead from indexing) anonymous wrote : - I'm not a fan of serialzation (I've had an incompatibility once due to upgrading a jdk). If needed, I marshal the objects, or use explicit hibernate mappings When we started this project no one really understood how hibernate worked, much less how to configure it. I think that any new variable classes we add will be implemented the same way as the native variables. anonymous wrote : - Creating an example is not trivial, but you expect 'us' to have/know tooling for debugging it.... ;-) Well, I wasn't looking for a tool for a specific problem, I was wondering if there were any general purpose DB tools for jBPM. (E.g., in a previous job we had a tool that would 'walk' the database and identify any inconsistencies that might cause future problems). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249959#4249959 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249959 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
