Are you sure you have enough threads configured for Tomcat or Jetty?  They
have a thread pool ya know.

ALSO:
Make sure your DB is not maxed out on I/O.

I had 1 JBoss machine, 1 DB machine, and one driver machine for an ECPerf
test.

JBoss machine:
dual-cpu 1.8 ghz AMD MP2200+, 1 gig ram, running Windows XP

DB machine:
Inspiron 8100 laptop running Oracle 8.1.7, 1 ghz, 512M ram, crappy disk
drive (4200rpms).

Driver machine(remote EJB client):
Dell desktop.  1 ghz, 512M ram.

1. Ran ECPERF with commit option 'A', got results, maxed performance with
240 concurrent users.
2. Switched one entity bean to commit-option 'B'
3. Reran test with 240 concurrent users.  Lost 30% in performance.

Conclusion:
DB maxed I/O maxed out.

Ran maxed out peformance test adding 8 threads extra to up to 24 threads.
Performance degraded about 2-5% with each increment beyond 240 concurrent
users.

XXXXXXXXXXXXXXXX
Bill Burke
Chief Architect
JBoss Group, LLC
XXXXXXXXXXXXXXXX

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Bonham
> Sent: Friday, November 22, 2002 11:17 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Jboss on WIN2000
>
>
> Thanks for posting your performance tuning procedures, they
> helped us a lot.
>
> We are load testing under a clustered environment with JBoss 3.2.0beta2.
> Here's our client and server load test machine configurations:
>
> Dual Intel Xeon 2.0 GHz Processor w/1G RAM
> RedHat Linux 7.3
> Kernel Version: 2.4.18-3smp
>
> The app uses JSPs and the EJB Facade pattern backed by an Oracle
> 9i database.
>
> We changed the STACK_SIZE to 256k and PTHREAD_THREADS_MAX to 16384 and
> recompiled glibc.  Using a C program were able to max out the number of
> pthreads at 12276, which is acceptable for our current needs.
>
> We're using Sun's JDK 1.3.1_05 and 1.4.1-b2 (both IBM and JRockit hung in
> other tests).
>
> However, when load testing around 500 concurrent users, JBoss seems to
> stop responding around 270 users.  It doesn't matter if we use
> Tomcat 4.0.6,
> 4.1.12, or Jetty 4.1.3, so now I'm trying to record some
> performance metrics
> using org.jboss.ejb.plugins.MetricsInterceptor.
>
> I know every application is different (and we could very well have bugs in
> ours), but in general, given a similar application and
> environment, how many
> concurrent users have others been able to scale to with JBoss?
>
> Thanks.
>
> --
> Chris Bonham
> President/CEO
> Third Eye Consulting, Inc.
> [EMAIL PROTECTED]
> http://www.thirdeyeconsulting.com
> 317.823.3686
> 317.823.0353 (FAX)
>
> Quoting Stephen Davidson ([EMAIL PROTECTED]):
> > Greetings.
> >
> > I have been getting more than adequate performance on some
> boxes running Linux 2.4.10 & 2.4.18.  The 2.4.18 does appear to
> be somewhat faster.  I have not had a chance to run a full load test on it
> > yet, however.
> >
> > The CPUs are 1.2Ghz AMDs, with 1.5GB 133Mhz SDRam.
> >
> > You did tune your kernels, though, right?  By default, the
> Linux kernels only allow 64 threads/process, and I think it was
> 1024 processes system.  And under these defaults, JBoss has a
> limit of about
> > 200 users, after which performance nose dives and stability degrades.
> >
> > For your convenience, I have attached a document for what we
> did to boost our threading capabilities.  I would be interested
> to here how it works for you.
> >
> > -Steve
> >
> >
> >
> > Bill Burke wrote:
> >
> > > Actually, I've been doing some performance tests
> lately(ECPERF) and Linux
> > > sucks, really sucks.  (Haven't tried the IBM threading model
> though).  Win2k
> > > is much better performing, although I hate to admit it.
> > >
> > > Bill
> > >
> > >
> > >>-----Original Message-----
> > >>From: [EMAIL PROTECTED]
> > >>[mailto:[EMAIL PROTECTED]]On Behalf Of
> > >>[EMAIL PROTECTED]
> > >>Sent: Thursday, October 03, 2002 4:32 AM
> > >>To: [EMAIL PROTECTED]
> > >>Subject: Re: [JBoss-user] Jboss on WIN2000
> > >>
> > >>
> > >>Why not upgrading to a better OS like linux or *BSD?
> > >>
> > >>On Thu, Oct 03, 2002 at 12:56:29PM +0530, Arijit Ghosh wrote:
> > >>
> > >>>I am using Jboss3.0 with Tomcat 4.0.3 with Win98. I plan to use with
> > >>>Win2000. ANyone has faced any issues that I need to take care of when
> > >>>deploying ? I DON'T want to use it as service for Win2000.
> > >>>
> > >>>Regards,
> > >>>  Arijit
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>-------------------------------------------------------
> > >>>This sf.net email is sponsored by:ThinkGeek
> > >>>Welcome to geek heaven.
> > >>>http://thinkgeek.com/sf
> > >>>_______________________________________________
> > >>>JBoss-user mailing list
> > >>>[EMAIL PROTECTED]
> > >>>https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >>>
> > >>--
> > >>MVH
> > >>Marius Kotsbak
> > >>Boost communications AS
> > >>
> > >>
> > >>-------------------------------------------------------
> > >>This sf.net email is sponsored by:ThinkGeek
> > >>Welcome to geek heaven.
> > >>http://thinkgeek.com/sf
> > >>_______________________________________________
> > >>JBoss-user mailing list
> > >>[EMAIL PROTECTED]
> > >>https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >>
> > >
> > >
> > >
> >
> > --
> > Java/J2EE Developer/Systems Integrator
> > 214-724-7741
> >
>
> > This is how I rebuilt glibc.
> >
> > I got the latest version of glibc(glibc-2.2.5.tar.gz) and
> glibc-linuxthreads
> > (glibc-linuxthreads-2.2.5.tar.gz) from www.gnu.org. I unzipped
> both of them
> > placing the thread libraries inside of the glibc directory (the threads
> > library is a component of glibc).
> >
> > Change the following C header files to up the threads. (I got this from
> > http://www.volano.com/linuxnotes.html)
> > In glibc/linuxthreads/internals.h, change the size of the thread stack
> > reserve from 2 megabytes down to 256 kilobytes (with a page
> size of 4,096
> > bytes):
> >
> > STACK_SIZE  (2 * 1024 * 1024) -> (64 * PAGE_SIZE)
> >
> > In sysdeps/unix/sysv/linux/bits/local_lim.h under
> glibc/linuxthreads, change
> > the Posix thread implementation limit from 1,024 per process to
> 8,192 per
> > process:
> >
> > PTHREAD_THREADS_MAX  1024 -> 8192
> >
> > Now, From inside the glibc directory execute the following command to
> > generate the make files:
> >
> > ../configure --enable-add-ons --prefix=/usr
> >
> > Then type make to build and then make install to install the libraries.
> > Finally execute ldconfig -v to update the library cache.
> >
> > I referenced http://www.imaxx.net/~thrytis/glibc/Glibc2-HOWTO-5.html in
> > building the new glibc. You dont have to follow the docs word for word
> > because its not a major change (like from glibc 5 to 6)
> >
> > Thats about it!
> >
> > Kyle
> >
> >
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to