Sponsored Content
Operating Systems Solaris Question: # of ldoms on T5240 with 2 T2 US 8 core Post 302862343 by bartus11 on Thursday 10th of October 2013 03:17:32 PM
Old 10-10-2013
"Theoretically" you could have more than 120 LDOMs (as your server has 128 processor threads), but performance on each of them would be very low.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

One Last Question about Core Files (distinguish) URGENT

now, what do you define as core files. there are some files outthere with the name perl.core, I-core.png, core.png I mean, are these classified as core files too??? i thought core files are simply files called "core". Please help me out this is urgent (2 Replies)
Discussion started by: TRUEST
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. Solaris

cannot plumb nxge on T5240

its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file. getting similar error on... (3 Replies)
Discussion started by: incredible
3 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. Solaris

Disable multithreading option on T5240

Hi Gurus Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core Regards (3 Replies)
Discussion started by: amity
3 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

Reducing Cores in T5240 server for meeting Oracle Core Licences

Hi I need to reduce cores on T5240 server for meeting Oracle Core licenses. For that I have install the LDOM packages & run below mention commands. bash-3.2# ldm list-config factory-default config_initial bash-3.2# ldm set-vcpu 32 primary bash-3.2# ldm list-config... (5 Replies)
Discussion started by: amity
5 Replies

9. 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
sched_thread_affinity(5)					File Formats Manual					  sched_thread_affinity(5)

NAME
sched_thread_affinity - adjust scheduler thread affinity VALUES
Failsafe Default Allowed values Any value in the range of is allowed. A value of indicates weak thread affinity, and the threads may run on different processors. A value of indicates strong thread affinity, and the threads will likely remain on the same processor. Recommended values Use the default value in normal cases. In special cases where it is imperative that threads run as quickly as possible, a value closer to may be used. However, this may lead to an increase in cache misses. Customers must evaluate the performance impact in their workload environment before changing the value of this tunable on production sys- tems. DESCRIPTION
The tunable defines on which processor a thread may likely run. A thread with lower affinity may move from one processor to another during its lifetime, whereas a thread with higher affinity will likely experience minimal movement across processors. A change in the value may have direct impact on system throughput and response times. A very small value may result in threads being run much quicker at the possible expense of higher cache misses, and a very large value may result in threads being run less frequently if they have run (or are running) on a loaded processor, with a possible benefit of improved cache affinity. I/O intensive applications are likely to benefit from a lower value for this tunable. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? Any increase in the value of this tunable will cause most threads to remain on the processor where they have run during their lifetimes. What Are the Side Effects of Raising the Value? Raising the value of the tunable may cause some threads to wait to run, even though there may be less loaded or idle processors in the sys- tem. When Should the Value of This Tunable Be Lowered? The tunable value should be lowered if the workload expects to run as quickly as possible, regardless of whether it is moved from processor to processor at the cost of possible increases in cache misses. What Are the Side Effects of Lowering the Value? Lowering may result in an increase in cache misses as threads begin to run on different processors during their lifetimes. What Other Tunable Values Should Be Changed at the Same Time? None. 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. Tunable Kernel Parameters sched_thread_affinity(5)
All times are GMT -4. The time now is 12:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy