Hi, On 28/07/11 10:19, Peter Dietz wrote: > Doing batch changes with a large number of changes will keep your > system busy, and the reindexing can take a while. I've noticed that > when we set the limit to be really high, it appears that nothing will > happen from the user's browser for 20+ minutes, so I've connected to > the server from the command line, and noticed that the reindexing > task was taking a long time, but still running. So you might be safe > with setting this to a really high number (several thousand), you'll > just have to have the patience to not disrupt it. But smaller / more > manageable batch sizes will complete in a reasonable amount of time. > With this set to 1000 or more, I'm guessing your more likely to run > into Out-Of-Memory errors
With one of 'my' repositories, when we increased the limit (to 1000 I think), completing the changes took so long that the Apache-Tomcat connection timed out. This meant that the user saw an error in their browser even though the changes actually went through fine. In our case we decided to stick with a lower limit to avoid confusion. Though 20 really does feel very low. cheers, Andrea -- Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
