Re: restricting search results (why?)

Hi Michal,

On May 10, 2004, at 13:52, Michal Skrzypek wrote:

>> Simply set your Envelope's fetch.limit to a high number (e.g.
>> 2147483647).
>     Oh my, oh my - that way you could be able to set your own version 
> of
> Google (TM) up and running in Just A Minute (TM). But, oh,
> unfortunately, you'll need to have a 2147483647 GHz Pentium MCML
> (just a guess) for this to work reliably and reasonably :))). So, not a
> big deal, you just have to wait till the next century... and voilla! :)

±0 will do also :)

That said, the issue is not related to CPU, but rather IO. If you can 
afford to store your entire data in RAM, you should see some very 
decent performances not matter what your data set it.

Also, what is time consuming is not the search per se, but rather 
loading all the objects that a search results represents. Your could 
mitigate this by removing the derived data displayed on the right side 
of the search result. But one way or another, IO is what slow down the 
app.

>     ... i just LOVE your kind of answers to that... ehm...
> "persistent self-answering e-mails" :)
>
> You the man, R! :)

You seem to be doing fine as well :)

Cheers,

R.




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3