On 11/2/07, Matt Hamilton <[EMAIL PROTECTED]> wrote:
> That may just end up causing delays periodically in transactions... ie delays
> that the user sees, as opposed to doing it via another thread or something.
> But
> then as only one thread would be doing this at a time it might not be too bad.
On 11/2/07, David Binger <[EMAIL PROTECTED]> wrote:
> > But wouldn't then all other threads get a conflict?
>
> If they are trying to do insertions at the same time as the
> consolidation, yes.
> This data structure won't stop insertion conflicts, the intent is to
> make them
> less frequent.
But
On Nov 2, 2007, at 10:18 AM, Christian Theune wrote:
Wouldn't a queue be a good data structure to do that? IIRC ZC already
wrote a queue that doesn't conflict:
http://svn.zope.de/zope.org/zc.queue/trunk/src/zc/queue/queue.txt
If you store key/value pairs in the queue, you can do a step-by-ste
Hi,
Am Freitag, den 02.11.2007, 09:56 -0400 schrieb David Binger:
> On Nov 2, 2007, at 8:39 AM, Lennart Regebro wrote:
>
> > On 11/2/07, Matt Hamilton <[EMAIL PROTECTED]> wrote:
> >> That may just end up causing delays periodically in
> >> transactions... ie delays
> >> that the user sees, as o
On Nov 2, 2007, at 8:39 AM, Lennart Regebro wrote:
On 11/2/07, Matt Hamilton <[EMAIL PROTECTED]> wrote:
That may just end up causing delays periodically in
transactions... ie delays
that the user sees, as opposed to doing it via another thread or
something. But
then as only one thread woul
On Nov 2, 2007, at 10:58 AM, Lennart Regebro wrote:
It seems to me having one thread doing a background consolidation one
transaction at a time seems a better way to go,
Maybe, but maybe that just causes big buckets to get invalidated
in all of the clients over and over again, when we could a
Matt Hamilton wrote:
David Binger mems-exchange.org> writes:
On Nov 2, 2007, at 6:20 AM, Lennart Regebro wrote:
Lots of people don't do nightly packs, I'm pretty sure such a process
needs to be completely automatic. The question is weather doing it in
a separate process in the background, o
Laurence Rowe wrote:
Essentially you end up with a solution very similar to QueueCatalog but
with the queue being searchable.
The pain is then in modifying all of the indexes to search the queue in
addition to their standard data structures.
In many applications it is acceptable to have a ca
On Fri, 2007-11-02 at 16:00 +, Laurence Rowe wrote:
> Matt Hamilton wrote:
> > David Binger mems-exchange.org> writes:
> >
> >>
> >> On Nov 2, 2007, at 6:20 AM, Lennart Regebro wrote:
> >>
> >>> Lots of people don't do nightly packs, I'm pretty sure such a process
> >>> needs to be completely
On Nov 2, 2007, at 6:20 AM, Lennart Regebro wrote:
Lots of people don't do nightly packs, I'm pretty sure such a process
needs to be completely automatic. The question is weather doing it in
a separate process in the background, or ever X transactions, or every
X seconds, or something.
Okay,
On 11/2/07, David Binger <[EMAIL PROTECTED]> wrote:
> I think that option would work. I think it would suffice to do a
> "Big.update(Small); Small.clear()" operation before a nightly pack.
Lots of people don't do nightly packs, I'm pretty sure such a process
needs to be completely automatic. The
On Nov 2, 2007, at 5:48 AM, Lennart Regebro wrote:
On 11/1/07, Matt Hamilton <[EMAIL PROTECTED]> wrote:
An interesting idea. Surely we need the opposite though, and that
is an
additional BTree with a very large bucket size, as we want to
minimize the
chance of a bucket split when inserting
On 11/1/07, Matt Hamilton <[EMAIL PROTECTED]> wrote:
> An interesting idea. Surely we need the opposite though, and that is an
> additional BTree with a very large bucket size, as we want to minimize the
> chance of a bucket split when inserting? Then we occasionally consolidate and
> move the it
David Binger mems-exchange.org> writes:
>
>
> On Nov 2, 2007, at 6:20 AM, Lennart Regebro wrote:
>
> > Lots of people don't do nightly packs, I'm pretty sure such a process
> > needs to be completely automatic. The question is weather doing it in
> > a separate process in the background, or ev
This is the 'batch' or 'distribute' pattern that crops up in many
fields.
The best path is normally to understand what the conflicts are, and
where the time is spent.
If in, this case, much time is spent in the preamble, and the actual
inserts are quick, then diving down one time through th
15 matches
Mail list logo
