Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <F7E4074F-AFF7-4B8E-B8C6-2FEF4C2FA9DB@marketingbrokers.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: java-user@lucene.apache.org
From: "Peter W." <peter@marketingbrokers.com>
Subject: In memory MultiSearcher
Date: Mon, 21 May 2007 14:38:48 -0700

Hello,

I have been using a large, in memory MultiSearcher that
is reaching the limits of my hardware RAM with this code:

       try
          {
          IndexSearcher[] searcher_a=
             {
             new IndexSearcher(new RAMDirectory(index_one_path)),
             new IndexSearcher(new RAMDirectory(index_two_path)),
             new IndexSearcher(new RAMDirectory(index_thee_path)),
             new IndexSearcher(new RAMDirectory(index_four_path)),
             new IndexSearcher(new RAMDirectory(index_n_path))
             };

	 MultiSearcher searcher_ms=new MultiSearcher(searcher_a);
	...
          }
       catch(Exception e)
          {
          System.out.println(e);
          }

For example, one of several indexes is 768MB. Is there possibly a  
better way to do this?

Regards,

Peter W.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org