performance issues on sun T5240

did you follow the Oracle recommendations for setting the solaris server for oracle? What soalris version are you running?

Dear oamrfarid,

We have followed oracles reccomendations,the operating system is Solaris 10

Rgds

Is there no solution to this problem ?

Are you sure that your swing code is set to properly take advantage of the multi-threading aspects of the new platform architecture you're running it on? Have you migrated the application, the database, or both to the 5240?

Dear Rowley,

even a simple query getting 500 records shows variation. There is threading in the application but one query which is atomic getting 500 recored cannot be threaded.

Rgds

can you show the specs of your system (memory, cpus, disks, etc)?

How big is your database? what type of file systems are you using?

Sun T servers are deceptive in that just having a lot more 'processors' does not necessarily mean every workload will run much better.  The T servers are best suited to workloads with a lot of multi-threaded tasks.  Any time you have a workload that comes together in a single or small number of threads, you will generally see worse performance on the T series servers than on a system with fewer, but faster, processors.

Memory is also a consideration.  Even if the workload is highly multi-threaded, you need a lot of memory to support that work.  If your previous system was processor bound using a dual-core Xeon (X4xx for example) with 16GB of RAM, you may find it memory bound on a T-series with equivalent memory.

12 GB RAM, two quadcore

Databse is almost empty around 1GB and we are using solaris native file system

You probably made a mistake by choosing for the T5240 without checking first if your application is suitable for this kind of machine.

A single thread on this machine will run like on a 600Mhz Sparc processor from 10 years ago. That's really, really slow. And probably equivalent to 10 times as slow as any modern CPU.

Only massively threaded tasks can tap into the power of this machine. That means that most types of applications can not. And even then, the latency on a single thread will always have a much higher latency that the same job on a traditional CPU that is moderately loaded.

So unless you have hundreds of users running many jobs simultaneously, you most likely made an expensive mistake (as have done many before you) by choosing for this coolthreads machine.

so if reduce the number of threads will i get better performance

or is there any other way of enhancing the performance please help

Your workload has to have a lot of threads.  Reducing the number of threads will make it worse.  You need a high concurrency and a large number of threads to get the best performance out of the T series.  Each of those threads has to have enough RAM to work as well.

>so if reduce the number of threads will i get better performance
>or is there any other way of enhancing the performance please help

If your application is not suitable for the T2000 series, nothing you do will increase performance significantly.

There are some tuning recommendations from Sun for certain types of apps that can help a little:

http://www.sun.com/servers/coolthreads/tnb/applications.jsp

But the only way to really get more performance out of this machine is to make the application use more threads. In many cases that's not an option, because the app needs to be redesigned for this. If this server is not suitable for you, there's only one option: get another type of server.

Btw, what's the application you're using ? How many users are using it ?

The number of users is around 25 but there some big data selects which are very very slow

close