[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-598) MassIndexer freezes when pool size is too low

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-598?pag... ] Sanne Grinovero edited comment on HSEARCH-598 at 4/1/11 4:48 AM: ----------------------------------------------------------------- Hi Adrien, thanks for all the insight. I don't think it's safe to open the connection in a different thread, as you say some containers might have issues with that; I'm not sure I could ask for opinions on this but it doesn't feel right, let's explore alternatives first. Also remember that opening a Session doesn't open a connection, and that a Session isn't designed to be passed to a different thread - so even hacking in an eager connection acquire there might be other issues. About your case, you have 34 different indexed entities? I think that reducing each worker to a single thread is likely going to hurt overall performance, did you consider launching the MassIndexer on each type sequentially? You can have it reindex a single type only - wondering if we should rather add an option to have it perform the different indexations in sequence, or in a maximum configurable parallelism. A patch would be awesome. Other possible approaches: * Have a background thread monitor advancement, possible killing off threads when a lock is spotted, so dynamically reducing parallelism to find a sweet spot. * Have the jobs use a comment Executor, to control global thread amounts (requires some care to have the same pipeline fully active) * Revert the design in such a way that each stage is able to handle all different entities - shouldn't be hard, and my original design was like that but it had a small performance overhead compared to the current pipelines. Could be fun to play with some work-stealing pattern, in which each thread starts working on the first part of the pipeline to switch stealing work from the subsequent phases when the output queue of the first stage is full. This way we could have a single pool of threads working on the first part only, and doing some of the subsequent work when he can't make progress in the first stage -> no deadlock possible, likely even better performance assuming the context switch decision can be written with efficient code. was (Author: sanne): Hi Adrien, thanks for all the insight. I don't think it's safe to open the connection in a different thread, as you say some containers might have issues with that; I'm not sure I could ask for opinions of colleagues but it doesn't feel right, let's explore alternatives first. Also remember that opening a Session doesn't open a connection, and that a Session isn't designed to be passed to a different thread - so even hacking in an eager connection acquire there might be other issues. About your case, you have 34 different indexed entities? I think that reducing each worker to a single thread is likely going to hurt overall performance, did you consider launching the MassIndexer on each type sequentially? You can have it reindex a single type only - wondering if we should rather add an option to have it perform the different indexations in sequence, or in a maximum configurable parallelism. A patch would be awesome. Other possible approaches: * Have a background thread monitor advancement, possible killing off threads when a lock is spotted, so dynamically reducing parallelism to find a sweet spot. * Have the jobs use a comment Executor, to control global thread amounts (requires some care to have the same pipeline fully active) * Revert the design in such a way that each stage is able to handle all different entities - shouldn't be hard, and my original design was like that but it had a small performance overhead compared to the current pipelines. Could be fun to play with some work-stealing pattern, in which each thread starts working on the first part of the pipeline to switch stealing work from the subsequent phases when the output queue of the first stage is full. This way we could have a single pool of threads working on the first part only, and doing some of the subsequent work when he can't make progress in the first stage -> no deadlock possible, likely even better performance assuming the context switch decision can be written with efficient code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira