Sponsored Content
Operating Systems Solaris Disable multithreading option on T5240 Post 302575830 by amity on Wednesday 23rd of November 2011 02:14:37 AM
Old 11-23-2011
Hi all

I came to know that if we use psradm command to disable all threads, except 0, 3 ,7,11 . Through this process we can disable the threads. But can any one tell me why cann't we disable 0,3,7,11 threads. I haven't done above process as my server is production. If any one have test T-series server having oracle database or application which is single thread base. As I believe above process will increase some or bit increase performance gain for singe thread application or database. But this process will not give us significant performance gain as per that person due to same clock speed of CPU. Looking for answer of my question.

Regards
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

KSH : Disable -x option

I have a KSH script. I want NO-ONE to call it with -x option. example : ksh -x /appl/u001/test_it_out.ksh Is there a way to know, from with in script, that they invoked the script with -x option. So that I can exit when they invoke it with -x option. please help. (2 Replies)
Discussion started by: vangaru
2 Replies

2. Solaris

raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0. I am trying to use raidctl but when I issue. raidctl -l I get Controller 1 Disk: 0.0.0 Disk: 0.1.0 So I try raidctl -c '0.0.0 0.1.0' -r 1 1 and I get "Array in use." I try (4 Replies)
Discussion started by: photon
4 Replies

3. Shell Programming and Scripting

How to disable Enable/Disable Tab Key

Hi All, I have bash script, so what is sintax script in bash for Enable and Disable Tab Key. Thanks for your help.:( Thanks, Rico (1 Reply)
Discussion started by: carnegiex
1 Replies

4. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS (4 Replies)
Discussion started by: rajasekg
4 Replies

5. Solaris

ufsrestore T5240

Hi Friends we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there? Regards Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies

6. Red Hat

SSL/TLS renegotiation DoS -how to disable? Is it advisable to disable?

Hi all Expertise, I have following issue to solve, SSL / TLS Renegotiation DoS (low) 222.225.12.13 Ease of Exploitation Moderate Port 443/tcp Family Miscellaneous Following is the problem description:------------------ Description The remote service encrypts traffic using TLS / SSL and... (2 Replies)
Discussion started by: manalisharmabe
2 Replies

7. Solaris

Cannot configure RAID on T5240

Hi ! I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before. I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl. ... (2 Replies)
Discussion started by: delavega
2 Replies

8. Solaris

Using a Modem on a T5-2 or a T5240

Hi Folks, Just a quick question - hopefully! I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
aio_req_per_thread(5)						File Formats Manual					     aio_req_per_thread(5)

NAME
aio_req_per_thread - desirable ratio between number of pending AIO requests and servicing threads VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilization of CPU time vs. I/O resources, four dynamic tunables are available to customize the behavior of this thread pool: aio_proc_threads(5), aio_proc_thread_pct(5), aio_req_per_thread(5), and aio_monitor_run_sec(5). Please see individual manpages for details on each of these tunables. The tunable specifies, on a per-process basis, the desirable ratio between the number of pending POSIX AIO requests and the number of threads in the AIO thread pool. The number of threads in the AIO thread pool is bounded by the tunables and but the tunable determines how the AIO thread pool behaves within that bound. determines how much the AIO thread pool grows as the number of outstanding AIO requests grows, by defining how many I/Os each thread will be responsible for. Who Is Expected to Change This Tunable? System administrators that run applications requiring heavy usage of POSIX AIO to filesystems. Restrictions on Changing This tunable is dynamic. Changes to to this tunable take effect immediately for new processes started after the change. They also impact existing processes, but the speed with which the changes propagate to running processes is determined by the tunable When Should the Value of This Tunable Be Raised? should be raised for applications that want to limit the number of threads used by the POSIX AIO subsystem. Applications would want to do this to either free up more process threads for other work, or to limit the level of concurrency inside POSIX AIO, perhaps to reduce load on physically limited I/O devices. What Are the Side Effects of Raising the Value of This Tunable? By allowing less threads for POSIX AIO requests, concurrency is reduced and AIO I/O requests will have to wait longer for servicing. This can result in increased latency and reduced POSIX AIO performance on systems whose I/O stack could otherwise handle heavier loads. On the other hand, less threads per request can result in less context switching, reducing the CPU utilization of POSIX AIO. When Should the Value of This Tunable Be Lowered? should be lowered when applications want to maximize the concurrency and performance of POSIX AIO requests. This should be done when an application does not need a large number of threads for other work. What Are the Side Effects of Lowering the Value of This Tunable? Lowering this tunable results in more threads being used by POSIX AIO to handle I/O requests, which could increase CPU usage and use up threads that applications might need for other work. On the other hand, POSIX AIO performance should increase. What Other Tunables Should Be Changed at the Same Time as This One? interacts with this tunable by setting a strict limit on the number of threads that can be used for POSIX AIO. interacts with this tunable by setting a limit on the number of threads that can be used for POSIX_AIO, but does so based on a percentage of the maximum number of allowable process threads. This allows the AIO thread pools to respond dynamically to changes in defines how often (in seconds) the AIO thread mechanism will monitor itself for adherence to the constraints defined by the tunables above. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), aio_proc_threads(5), aio_proc_thread_pct(5), aio_monitor_run_sec(5). Tunable Kernel Parameters aio_req_per_thread(5)
All times are GMT -4. The time now is 04:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy