03-03-2012
Reducing threads on T5140
Hi All,
We have a T5140 server which has 128 threads in total. Is it possible to reduce the number of threads per core through some configuration changes? I am sorry for being so naive but I am one on this.
Why would I like to do this? Unfortunately we have this for an Oracle Database Server and it is giving terrible performance. We have an M Series in production and have excellent performance there. So was just wondering if it is possible to reduce the number of threads like in M series to improve some performance
9 More Discussions You Might Find Interesting
1. HP-UX
Hi,
I've entered the HP-UX 11i server in single user mode, and increased the filesystem /usr by mistake using
lvextend -l 3092 /dev/vg00/lvol7
extendfs /dev/vg00/rlvol7
I put small letter "l" instead of "L".
and as a result of this mistake the /usr take all the free space in the volume... (2 Replies)
Discussion started by: elshamy_s
2 Replies
2. Solaris
Hi,
I have a brand new SUN T5140 machine. I am trying to install Solaris 10 on the box. When I go to the machine using a KVM session I can see a blank screen , how can I get to the OK prompt to start the installation.
Thanks,
Suresh (10 Replies)
Discussion started by: gunnervarma
10 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Solaris
What is the serial port on the T5140 used for. (4 Replies)
Discussion started by: pgsanders
4 Replies
5. Solaris
Hi,
I need configure this server for two zones (oracle and glassfish). Server has 2CPU 8cores = 128vcpu and 16 GB RAM.
I am interested in mainly the division of the processor and memory.
What was the configuration that best for Oracle zones? (4 Replies)
Discussion started by: bieszczaders
4 Replies
6. Solaris
Hi all,
I use latest bind 9.6.1, brand-new T5140 Sun Server, 10u8 Solaris OS, Mar-2010 OS patch to configure a caching dns server.
But bind always hang up when process/cache is reaching to 500 Mb ( Though 'prstat -a' check )
Can anyone help me a solution for this problem, i will greatly... (0 Replies)
Discussion started by: tien86
0 Replies
7. Solaris
I've been busy and fell behind on Sun/Oracle. Forgive me if too basic. I welcome brief, cryptic, or advanced replies. I also welcome noobie information since I may have no clue what's up at the moment.
Problem statement:
I inherited a computer to set up. I would rather not figure out 8 months... (1 Reply)
Discussion started by: Nevyn
1 Replies
8. Solaris
I have a T5140 and cannot find the power switch -is there an on/off button? Good grief !
Thank you in advance.
joe (3 Replies)
Discussion started by: joboy
3 Replies
9. AIX
The root filesystem was mirrored, someone/something stopped mirroring, and increased / and /home to ridiculous values (/ got increased to 102gb and its only using 4.3gb, so 98gb is free). Can I reduce the / (/dev/hd4) filesytem down WITHOUT corrupting the the OS?
I would do a: chfs -a size=10g... (6 Replies)
Discussion started by: mrmurdock
6 Replies
LEARN ABOUT OSF1
sched_yield
sched_yield(3) Library Functions Manual sched_yield(3)
NAME
sched_yield - Signals scheduler a willingness to yield to another thread.
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h>
void sched_yield(void);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
None
DESCRIPTION
This routine forces the running thread to relinquish the processor until it again becomes the head of its thread list. This routine noti-
fies the thread scheduler that the current thread is willing to release its processor to other threads of equivalent or greater scheduling
precedence. (A thread generally will release its processor to a thread of a greater scheduling precedence without calling this routine.)
If no other threads of equivalent or greater scheduling precedence are ready to execute, the thread continues.
This routine can allow knowledge of the details of an application to be used to improve its performance. If a thread does not call
sched_yield, other threads may be given the opportunity to run at arbitrary points (possibly even when the interrupted thread holds a
required resource). By making strategic calls to sched_yield, other threads can be given the opportunity to run when the resources are
free. This can sometimes improve performance by reducing contention for the resource.
As a general guideline, consider calling this routine after a thread has released a resource (such as a mutex) that is heavily contended
for by other threads. This can be especially important if the program is running on a uniprocessor machine, or if the thread acquires and
releases the resource inside a tight loop.
Use this routine carefully and sparingly, because misuse can cause unnecessary context switching which will increase overhead and degrade
performance. For example, it is counter-productive for a thread to yield while it holds a resource that the threads to which it is yielding
will need. Likewise, it is pointless to yield unless there is likely to be another thread that is ready to run.
RETURN VALUES
None
RELATED INFORMATION
Functions: pthread_attr_setschedparam(3), pthread_setschedparam(3)
Manuals: Guide to DECthreads and Programmer's Guide
delim off
sched_yield(3)