Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Solaris 8 x86 or RedHat 7 for NSF server Post 2096 by Neo on Wednesday 18th of April 2001 07:53:49 PM
Old 04-18-2001
Linux will generally outperform Solaris in many CPU related benchmarks, all other things equal. Not sure about network interface performance. Networking performance has always been a weaker area in Linux. Regardless, both will work just fine.

Normally there are other concerns more important than raw hardware performance, including: training, existing skill sets, requirements for commercial support and other corporate factors. The ultimate decision should take into consideration the human, support and sustainability factors and weigh them appropriately.

[Edited by Neo on 04-18-2001 at 08:03 PM]
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

2. UNIX for Dummies Questions & Answers

setup a DNS server for my redhat server

Using Redhat Linux Enterprise AS 4 can someone teach me how to setup a dns server for my webserver? i've registered a domainname at mydomain.com but when i type in the domain i register i cannot enter to my webserver. someone told me that it is related with the DNS setting on my server. i've... (2 Replies)
Discussion started by: kaixiang88
2 Replies

3. Solaris

network driver not detecting in solaris 10 X86 on HPDL380G5 Server

I have installed solaris10 x86 on HP DL380 G5 Server, but network card is not getting detected. i have installed the network driver, downloaded from the following link HP ProLiant DL380 G5 Server series- Download drivers and software - HP Business Support Center Can any one suggest me how to... (1 Reply)
Discussion started by: raj.chinnu
1 Replies

4. Solaris

How to configure Proxy Server in Solaris 10 (X86)

Hi , I have installed solaris 10 on x 86 architecture. Now i want to configure this system as Proxy Server. I am new to the solaris. Please help me how can i configure this. Which packages or patches are needed ? or Which files have to be modify ? Please help me to resolve. Thanks and... (0 Replies)
Discussion started by: raviraj001
0 Replies

5. Red Hat

RedHat vs Solaris x86

Can some one give me few points as why we can choose RedHat Linux over Solaris x86 ? I want to give reasons to my upper management to start using RedHat Linux , currently we are 100% Solaris Shop (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Solaris: clnt_create fails on solaris x86

Hi, I am facing an issue with Solaris x86 machine Machine Details: uname -a SunOS sol10-64 5.10 Generic_137138-09 i86pc i386 i86pc .............................. Description: I am trying to register a programm with proramm ID 300760 with version number 1, and tryint to create a... (0 Replies)
Discussion started by: DivakarAdari
0 Replies

7. UNIX for Dummies Questions & Answers

enable all operations to use a proxy server , redhat server

Hi, i would like to enable all operations/connections to use a proxy server in a redhat server , witch file should i config to get this for all conections .... Thanks (0 Replies)
Discussion started by: prpkrk
0 Replies
alt(7)							 Miscellaneous Information Manual						    alt(7)

NAME
alt - DEGPA Gigabit Ethernet interface SYNOPSIS
config_driver alt DESCRIPTION
The alt interface provides access to Gigabit Ethernet (1000Mbs) through the DEGPA device. The interface supports full-duplex operation in a switched or point-to-point configuration, and provides the following features: The interface has Link Autonegotiation enabled by default. Some switches do not support Link Autonegotiation. To turn Link Autonegotiation off, use the following command: # lan_config -ialt0 -a0 Note that you may add this command to the /etc/inet.local file to preserve the set- ting of Link Autonegotiation across system restarts. JUMBO packets are disabled by default. JUMBO packets provide a non-standard larger packet size. This enables the interface to carry more data with less CPU overhead. To enable JUMBO packets, use the following command: # ifconfig alt0 ipmtu 9000 Note that there are several interoperability issues with using JUMBO packets (for example, if your switch goes from 1000Mbps to a 100Mbps client, JUMBO packets will not work on a 100Mbps LAN). In order to use JUMBO frames, you will need a switch that supports JUMBO frames or a point-to-point configuration with a partner that supports JUMBO frames. Receive flow control is enabled. There is currently no way to turn this off. Gigabit Ethernet performance with TCP/IP depends on several factors. Some of the influencing factors are as follows: The speed at which data can be delivered to the interface influences throughput. If your CPU(s) are busy doing several tasks, the task using Gigabit Ethernet may not get enough run time to deliver packets. In general, faster CPUs will deliver better throughput. Fast access to the PCI bus is critical for high throughput. Using a 64-bit PCI slot will give you better performance and use less PCI resources than a 32-bit PCI slot. Putting the interface on the same PCI bus as other peripherals will degrade throughput. Each system type may also have different PCI-to- host speed considerations (the speed at which the PCI-to-host hardware allows the device to operate). The standard TCP/IP applications (for example, ftp and rcp) are not designed to run at Gigabit speeds. TCP applications that expect performance should use a message size of 65000 bytes and a window size of 128000 bytes. Even when an application is modified to use these settings, high throughput may not be attainable. This is particularly true when an application is waiting for data to send (data from a disk, for example). ERRORS
The following diagnostic and error messages contain relevant information provided by the alt interface, and are displayed to the console. Each message begins with the adapter identification, including the number of the adapter. The alt interface could not find adequate I/O addressing on this system to operate. This is a fatal error, and the DEGPA-SA will not operate on this system. There was a memory alloca- tion problem or the device initialization has failed. This is indicative of a hardware problem. Indicates that the Gigabit Ethernet link is up. The Autonegotiated keyword indicates that the link was autonegotiated. Note, this will only be on if autonegotiation is enabled). The ReceiveFlowControl keyword indicates that Receive Flow control is enabled on the link. Indicates that the link is no longer estab- lished. No communication will occur over the link while it is down. RELATED INFORMATION
Commands: ifconfig(8), lan_config(8) Files: inet.local(4) Network information: arp(7), inet(7), netintro(7) delim off alt(7)
All times are GMT -4. The time now is 10:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy