Should we keep the HOLDER.DEFAULT pattern to not create the default stop
set if not needed (when there is a custom building)?
Le mar. 2 juil. 2024 à 01:45, Chris Hostetter a
écrit :
>
> : There's also one other problem with those sets: Unfortunately they are
> : modifiable, because they are not
: Should we keep the HOLDER.DEFAULT pattern to not create the default stop
: set if not needed (when there is a custom building)?
I did not mean to imply that i think we eliminate the HOLDER
pattern/optimization -- i just didn't include it in my "(simplified)"
example to try and focus on the m
Hi all - I wonder if anyone else is observing weird email behavior
from Github. I'm starting to see emails generated from PRs and issues
that are wildly out of date. Like one dated yesterday that was
generated from a comment that is weeks old. And I am missing many
current updates -- as if there is
On Tue, Jul 2, 2024 at 1:59 PM Michael Sokolov wrote:
>
> Hi all - I wonder if anyone else is observing weird email behavior
> from Github. I'm starting to see emails generated from PRs and issues
> that are wildly out of date. Like one dated yesterday that was
> generated from a comment that is w
ah that helps, thanks
On Tue, Jul 2, 2024 at 2:41 PM Robert Muir wrote:
>
> On Tue, Jul 2, 2024 at 1:59 PM Michael Sokolov wrote:
> >
> > Hi all - I wonder if anyone else is observing weird email behavior
> > from Github. I'm starting to see emails generated from PRs and issues
> > that are wild
Hi Ben,
I am working on something very close to what Michael Sokolov has done.
I see OOMs on the Writer when it tries to index 130M 8 bit / 4 bit
quantized vectors on a single big box with a 40 GB heap, with HNSW disabled.
I've tried indexing all the vectors as plain vectors converted to floats
co
