If a library has a lot of items (1000+) on a single record, such as all of National Geographic on the same record, it will cause slowdowns in the system. Specifically can make (at least) the following things difficult: -searching -loading records -holds Having a limit would be helpful.
Introducing a limit seems not the ideal solution, and a reasonable limit might be different depending on your system's resources and setup. I like the work on the item table that seems one way to make this work better and is waiting for testing: bug 33945, 33568
(In reply to Katrin Fischer from comment #1) > Introducing a limit seems not the ideal solution, and a reasonable limit > might be different depending on your system's resources and setup. I like > the work on the item table that seems one way to make this work better and > is waiting for testing: bug 33945, 33568 Katrin, I think you're correct that those bugs should fix this issue. Thanks! Lisette
Both of the other bugs have been fixed. I'm going to close this one *** This bug has been marked as a duplicate of bug 33568 ***