"Chris Hostetter" <[EMAIL PROTECTED]> wrote:
> A dirty broken patch is more still better then no patch at all -- worst
> case scenerio: nothing happens; typical scenerio: you get some eyeballs
> reading your patch even if they can't apply it; best case scenerio:
> someone else is really excited b
: It doesn't apply to SVN head just yet (I need to update the payloads
: commit -- Michael: you returned the favor here!), it's not yet thread friendly
: (though I can do that after first patch), it messes up the merge policy
: when you flush by RAM and not by document count (this is actually alre
"Marvin Humphrey" <[EMAIL PROTECTED]> wrote:
> > I think some of these changes are similar to how KinoSearch builds a
> > segment.
>
> Yup... sounds familiar. ;)
>
> > I'm still working through some lingering issues before I can make a
> > clean patch,
>
> Well, where is it? Don't keep it a
Woops! I meant for this to go to java-dev...
Mike
On Mon, 19 Mar 2007 08:09:37 -0400, "Michael McCandless" <[EMAIL PROTECTED]>
said:
> Hi,
>
> I've been looking into improving performance of IndexWriter,
> specifically how it makes use of RAM to buffer added documents.
>
> I've created a new
