Sounds great. Could you create an issue in JIRA (http://issues.apache.org/jira/browse/NUTCH) issue about this, and mark it as an "improvement". That way we can track progress on it, and attach patches and progress.
Thanks, Chris On 1/5/06 1:56 PM, "Raghavendra Prabhu" <[EMAIL PROTECTED]> wrote: > Ya we shud do this . > > It will considerably improve performance > > We shud start building upon this . > > Rgds > Raghavendra Prabhu > > > On 1/6/06, Chris Mattmann <[EMAIL PROTECTED]> wrote: >> >> Hi Raghavendra, >> >> I think that this is a good idea. What about a commons-pool >> (http://jakarta.apache.org/commmons/pool/) implementation? The nutch bean >> pool could be built using the basic API classes from this package... >> >> Cheers, >> Chris >> >> >> On 1/5/06 1:43 PM, "Raghavendra Prabhu" <[EMAIL PROTECTED]> wrote: >> >>> What i am saying is NutchBean is not instantiated in the servlet context >> and >>> garbage collection. >>> >>> The Server has a way of allocation NutchBean to users who request from >> its >>> base and give it to them . >>> >>> It must also free the NutchBeans either periodically or when the number >> of >>> nutchbeans have reached a size >>> >>> Raghavendra Prabhu >>> >>> >>> On 1/6/06, Raghavendra Prabhu <[EMAIL PROTECTED]> wrote: >>>> >>>> No i dont think so >>>> >>>> What i am suggesting is we have nutch beans instantiated and we store >> it . >>>> >>>> Whenever an user comes and searches ,he will be given a NutchBean . >>>> >>>> >>>> After he searches he returns it to the pool and during the same time >> when >>>> some one searches he would get the same bean (note new bean is not >> created ) >>>> >>>> Only if a bean is not available ,does a new bean get created . >>>> >>>> This makes it faster as different users share the same NutchBean and it >>>> does not create a new nutchbean >>>> >>>> Note:NutchBean is shared across different users whereas right now it is >>>> only for a single user and garabage collected >>>> >>>> Here we control the NutchBean instantiation and we have to come up with >> a >>>> way to free it . >>>> >>>> >>>> >>>> >>>> On 1/6/06, Byron Miller <[EMAIL PROTECTED]> wrote: >>>>> >>>>> If i'm not mistaken doesn't the opensearch servlet get >>>>> around this issue? You could then post process the xml >>>>> through a stylesheet/css or your favorite scripting >>>>> language. >>>>> >>>>> -byron >>>>> >>>>> --- Raghavendra Prabhu <[EMAIL PROTECTED]> wrote: >>>>> >>>>>> Right now >>>>>> >>>>>> Whenever an user comes and searches ,a NutchBean is >>>>>> created >>>>>> >>>>>> We should have a mechanism where this nutchbean is >>>>>> pooled .I mean is created >>>>>> and stored so that it can be given to the user >>>>>> >>>>>> Immediately after the user has used the Nutch Bean >>>>>> ,he returns it back >>>>>> >>>>>> (example at orkut ,we get a message saying doughnut >>>>>> not available) >>>>>> >>>>>> This will make search result faster and more >>>>>> efficient >>>>>> >>>>>> Only when paraller users are there will nutchbeans >>>>>> get created >>>>>> >>>>>> Any comments on the above issue >>>>>> >>>>>> >>>>>> Rgds >>>>>> Prabhu >>>>>> >>>>> >>>>> >>>> >> >> >> >> ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Nutch-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-general
