What kind of practical sense does it make to batch 400k objects? I can no imagine single usecase where one<br>would be interested in walking through such an amount of objects manually. Better organize your data in a more<br>
handy way or implement some search logic for bringing the batch size to a number of relevant object.s<br><br>-aj<br><br><div class="gmail_quote">On Mon, Nov 2, 2009 at 00:04, Ken Ara <span dir="ltr"><<a href="mailto:feedreader@yahoo.com">feedreader@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;" valign="top">
<br><br>Under our setup, beyond 300-400,000 contained objects, the batching provided by getBatchObjectListing becomes unusable. I've seen this problem mentioned somewhere but never any hint of a solution.<br><br></td>
</tr></tbody></table><br></blockquote></div><br>