Sponsored Content
Top Forums UNIX for Dummies Questions & Answers With Linux do Hardware Brands Matter? Post 302584190 by bggibson on Thursday 22nd of December 2011 10:53:41 AM
Old 12-22-2011
With Linux do Hardware Brands Matter?

We have run software on Dell Servers w/ Windows and seen the performance degrade overtime. We switched to an IBM server w/ AIX and have not seen the same performance degradation over time. In fact, the IBM servers are at least five years old and continue to preform well at the same level.

How much of that is hardware vs. operating system?

If we ran the Dell with Linux would we have seen the same performance degradation?

Where is this leading? I am looking to setup a server environment to install and learn enterprise software. Based on experience I think the right operating system to select is Linux but I am not clear on the hardware I should look for. I am thinking I would like a multiprocessor machine so I may partition it into different LPARs and install the software in a distributed fashion as it would be in a real enterprise. My budget is about $1000. HW/OS recommendations welcome.
 

8 More Discussions You Might Find Interesting

1. Linux

What hardware will LINUX run on 386/486 ?

I'm really new to this and I want to learn UNIX/LINUX and saw the post about setting up a server to use everyday to practice. I have an old 386 PC and a 486 PC sitting around. Can they be reformatted and used to run UNIX/LINUX on as a network. (4 Replies)
Discussion started by: Barkingmad
4 Replies

2. Hardware

Linux Hardware Compatibility Guide (2007 HOWTO)

Before posting questions about Linux hardware, it is a good idea to check the Linux Hardware HOWTO guide (Last Update: 2007-05-22) However, this HOWTO has not been maintained since 2007 and it out-of-date. (0 Replies)
Discussion started by: Neo
0 Replies

3. Windows & DOS: Issues & Discussions

How To Check Hardware RAID On Windows and Linux

Hello, I have Win NT server running and I want to know how can I get Hardware RAID settings without rebooting the server? Thanks in advance. (2 Replies)
Discussion started by: sureshcisco
2 Replies

4. UNIX for Dummies Questions & Answers

What are the two ways the hardware clock can be configured under Linux?

What are the two ways the hardware clock can be configured under Linux? Thanks (3 Replies)
Discussion started by: lemon_06
3 Replies

5. UNIX for Dummies Questions & Answers

Linux on custom hardware

I would like to configure a bare minimum Linux with internet browser on a system with Flash & RAM (but no harddisk or any other nonvolatile storage). Please advise. (5 Replies)
Discussion started by: rherb
5 Replies

6. Hardware

Requirment are without password to get hardware info in the the linux using Qt?

Dear All, I have developed one application in the Qt Creator. I have one requirment for get hardward information in the Linux system, Then i try dmidecode using and run in Qt.It will occur error message for "dev/mem" permission denied". So i try to terminal to run sudo ./application. it will ask... (1 Reply)
Discussion started by: JGops79
1 Replies

7. Shell Programming and Scripting

Help with Linux hardware fault script in Perl

Hello, I am working on a Perl script to run from an AIX Nim server to extract hardware errors from our Linux server using various forms of grep statements - I have all my hosts in a text file and a command is run from the nim server to each host to pull out data from /var/log/messages and... (5 Replies)
Discussion started by: neilh1704
5 Replies

8. Hardware

Does this hardware works with Linux

Hello folks, I pretend acquire this hardware: 1-Motherboard Asus Skt1151 - H110M-A/M.2 (https://www.asus.com/pt/Motherboards...cifications/); 2-Intel i5 6400 2.7Ghz QuadCore Skt1151; or 2-Intel i5 6500 3.2Ghz QuadCore Skt1151; 3-Dimm 8GB DDR4 Kingston CL15 2133Mhz; Obvious I pretend... (1 Reply)
Discussion started by: enodev
1 Replies
timeslice(5)							File Formats Manual						      timeslice(5)

NAME
timeslice - scheduling interval in clock ticks per second VALUES
Failsafe Where defines the number of clock ticks per second for which the system is configured. Default Where is equal to Allowed values Any value in the range of is allowed. A value of indicates no timeslice based scheduling preemption, and threads will continue to run until they voluntarily switch out or higher priority threads preempt them. Recommended values Use the default value in normal cases. In special cases where quicker round robin scheduling is required, a value of may be used. How- ever, a change in value may have a direct impact on system performance. Customers must evaluate performance impact in their workload envi- ronment before changing the value on production systems. DESCRIPTION
The tunable defines the scheduling time interval that a thread may execute on a processor before the kernel scheduler will context switch out the thread for other same priority threads to run. When a thread starts executing on a processor, the thread is set up to run for the number of ticks in the tunable. On every clock interrupt that a thread is found executing, the time quantum balance for the thread is decremented, and when the balance reaches zero, the thread is context switched out. The value controls one method of user preemption that the operating system implements. A larger value will reduce preemption of running threads; however, there are other reasons for user preemption of threads, and the tunable has no control there. A change in the value may have direct impact on system throughput and response times. A very small value may result in too many context switches, and a very large value may result in the starvation of runnable threads. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect at the next reboot. When Should the Value of This Tunable Be Raised? Since the tunable is globally applicable to all threads (except in the system, irrespective of their scheduling policies and priorities. Any increase in value of this tunable will give equal time quantum boost to all threads. If the system has too many context switches due to preemptions, caused by higher priority threads, you can raise the value to provide more time for lower priority threads to execute when they get scheduled, because higher priority threads will preempt the lower priority threads when they become runnable. What Are the Side Effects of Raising the Value? Raising the value of the tunable may cause starvation of some threads, as they have to wait longer for their turn to execute. This may cause performance throughput issues. When Should the Value of This Tunable Be Lowered? The tunable value should be lowered if better turnaround in response time is required at the cost of additional context switches. When the system does not have too many compute intensive applications, threads will block and preempt much more frequently without utilizing their complete time quantum. What Are the Side Effects of Lowering the Value? The lowering of the tunable will result in many more context switches which will increase the time spent in SYSTEM space and less time spent in USER space. Also, the applications that are compute intensive will suffer performance degradation. 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 timeslice(5)
All times are GMT -4. The time now is 06:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy