-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 3:28 AM
To: [EMAIL PROTECTED]
Subject: Re: [Nutch-general] RE: Please help: Tomcat problem, Paginating
with optimization (Likegoggle)
Dear Chirag,
Thanks for your help, you are very helpfull.
I tested resin (opensource) and tomcat with jmeter. The resin is better in
this case.
The tomcat breakdown after 4000 calls, resin too, but after 1 minute go back
to the live.
>2. Tomcat runs out of memory and required manual restarts every 6-8
>hours, Resin auto starts itself around once a day (again, this is a
>memory leak in our code, but having the auto start is a great feature)
The bug in Nutch, or your specialized code?
- OUR CODE
>That being said, as you can see for us Resin was the choice as we
>needed the reliability and better logging. For someone who is not going
>to change a lot of the code Tomcat should work very well -- so use what
>you are most comfortable with for know and don't get bogged down learning
something new.
>Once you are ready for production then you can take a look at Resin.
I don't found better logging, I found only access log.
- FOR MOST INSTANCES YOU WONT NOTICE THE DIFFERENCE. WHEN YOU GO BUG HUNTING
IT WILL BECOME APPARENT!
>In this case I would use 5MM -- and try to give the Word server 4GB ram
>(as that's the maximum that can fit on a low-end server using the
>cost-effective 1GB sticks)
I don't understand your suggestion. What is the '5MM'? This is 5Million
Pages / 4 GByte RAM / 1 server?
YES, but I realized you're talking of 500,000 documents. It that case 1GB
ram should be sufficient.
Thanks,
Ferenc
