Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of georges@mhsoftware.com
 designates 209.169.14.178 as permitted sender)
From: "George Sexton" <georges@mhsoftware.com>
To: "'Tomcat Users List'" <users@tomcat.apache.org>
References: <008001cad73a$72803400$57809c00$@com>
 <4bbe0a26.c501be0a.37c3.04dd@mx.google.com>
In-Reply-To: <4bbe0a26.c501be0a.37c3.04dd@mx.google.com>
Subject: RE: Tomcat scalability setting - need help please
Date: Thu, 8 Apr 2010 11:49:54 -0600
Organization: MH Software, Inc.
Message-ID: <009301cad743$e5fbb720$b1f32560$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcrXKtelSb+mVSLuTnyeNhE8OJxwTwAD0jZAAABRVnAAAgbXUA==
Content-Language: en-us

Clearly instantiating millions of objects is not a strategy for scalability.

You're going to have to re-structure your code to reduce the memory
footprint of each session.

Why is your result set returning a million rows? No human would want to see
that much data.

You need to restructure your queries and navigation design so that it
doesn't do this.

George Sexton
MH Software, Inc.
303 438-9585
www.mhsoftware.com


> -----Original Message-----
> From: Cin Lung [mailto:cinlung@gmail.com]
> Sent: Thursday, April 08, 2010 10:53 AM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat scalability setting - need help please
> 
> Hi George
> 
> Your remark is almost correct. What I did is that I store the result of
> the
> resultset (which can go up to million lines of rows) in a batch of Java
> beans. Then I set the beans to the HTTP Request and pass them to the
> receiving JSP.
> 
> But I do remember to return the connection to the pool. I also try to
> kill
> the statements, result sets, etc by setting them to null. But I realize
> that
> java might wait for the memory to be cleared by the garbage collector.
> 
> This goes back to my second problem. If the user closes the browser,
> the
> request object form the servlet would lost its way to return the
> result. And
> this will hog the tomcat performance for a while.
> 
> Any tips would greatly be appreciated.
> 
> TIA
> Rendra
> 
> -----Original Message-----
> From: George Sexton [mailto:georges@mhsoftware.com]
> Sent: Thursday, April 08, 2010 11:42 PM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat scalability setting - need help please
> 
> 
> > -----Original Message-----
> > From: Pid [mailto:pid@pidster.com]
> > Sent: Thursday, April 08, 2010 8:49 AM
> > To: Tomcat Users List
> > Subject: Re: Tomcat scalability setting - need help please
> >
> > When you run the query in your application how are you doing it, e.g.
> > by
> > calling a stored procedure, or by executing exactly the same SQL
> > statement?
> >
> 
> 
> Most likely the application is storing result sets on the session.
> 
> 
> 
> George Sexton
> MH Software, Inc.
> 303 438-9585
> www.mhsoftware.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org