My thought is that this should be handled by limiting the *total* size of all updates in one call to be limited the same way that *single* update sizes are limited now.
On Thu, Dec 16, 2010 at 11:04 AM, Henry Robinson <[email protected]> wrote: > This should be a cautionary note on performance, however: as there is no > parallelism in the execution of updates (although there is plenty in the > serialisation process) we should build a mechanism to constrain how much > work this operation can perform, otherwise there's a danger of hurting > throughput for all clients of a cluster. >
