Hello Scott!
I think your index is just not large really. My Sharehound's indexes of my
corporate LAN is about 10G/10mlns of (really small) documents now, and queries
get really little time, less than a second for non-sorted queries and some more
for sorted. The machine is some P4 with 1G RAM. I u
I recently played around with a 2 million doc index of docs that averaged
between 2-10k. The system had 4 gig of ram and a 3 gig dual core proc (not
using a parallel searcher to take advantage of the extra core)...pretty
beefy, but with 4 times the docs your talking about. I didn't see a query
tha
Hello Scott!
I think your index is just not large really. My Sharehound's indexes of my
corporate LAN is about 10G/10mlns of (really small) documents now, and queries
get really little time, less than a second for non-sorted queries and some more
for sorted. The machine is some P4 with 1G RAM. I u
Lots of memory will help a lot. I have a customer of DBSight and he is
using Intel Core Duo, and configure everything in memory. The index
size is about 700M. When I checked his system's average response time,
it's 12ms! I guess you can estimate what you will get from your beefy
machine.
So it ma
"Scott Smith" <[EMAIL PROTECTED]> wrote on 12/10/2006 14:14:57:
> Supposed I want to index 500,000 documents (average document size is
> 4kBs). Let's assume I create a single index and that the index is
> static (I'm not going to add any new documents to it). I would guess
> the index would be a
Supposed I want to index 500,000 documents (average document size is
4kBs). Let's assume I create a single index and that the index is
static (I'm not going to add any new documents to it). I would guess
the index would be around 2GB.
Now, I do searches against this on a somewhat beefy mach
