[KinoSearch] serializing safely

[Hans Dieter Pearcey]

On Thu, Jun 14, 2007 at 07:09:12AM -0700, Marvin Humphrey wrote:
> 
> On Jun 14, 2007, at 4:50 AM, Hans Dieter Pearcey wrote:
> 
> >I had been thinking of putting it into an Apache::Session.
> 
> Serializing a Searcher so that the state of the *Searcher* *object*  
> can be preserved between requests?  That wouldn't aid performance,  
> even if Searcher could be serialized.
> 
> What you're describing is analogous to serializing a filehandle --  

That's more or less what I figured.

> >My app primarily differs in that I was planning on having many  
> >invindexes, two
> >or three per user, so opening them all at program start would  
> >probably be
> >inefficient (there are several hundred of them).
> 
> OK.  With that architecture, you'll need to factor in the time it  
> takes to begin reading from any one of those invindexes.

It may be a stupid architecture; I'm not really very experienced with
invindexes.  I want to index about 250G of email, which seems like a lot to me,
so I'm assuming that partitions will be useful (since each user only searches
their own email).  Am I prematurely optimizing?

hdp.