Skip to main content

AMD Opteron vs Intel Itanium





Recently, I attended a seminar on Grid Computing and HPC. The organizer invited an Indian speaker, a sales director of SUN India, Mr Mohan. In his brilliant speech, many useful information gathered by me especially the decision made by SUN to opt for AMD Opteron on many its HPC products instead of Intel Itanium (in terms of commodity 64-bit CPU).

Why Opteron?
These are the reasons (briefly):

1. Allows end users to run their existing installed base of 32-bit applications and operating systems at peak performance, while providing a migration path that is 64-bit capable.

2. HyperTransport technology - provides a scalable bandwidth interconnect between processors, I/O subsystems, and other chipsets. This feature is not available in Itanium.

3. Integrated DDR DRAM Memory Controller - this memory is integrated in CPU itself. For Itanium, the memory is outside of CPU. According to Mr Mohan,Itanium introduced FSB (Front Side Bus) to connect CPU to external RAM. This increases latency.

4. Low-Power Processors - the AMD Opteron processor offers industry-leading performance per watt making it an ideal solution for rack-dense 1U servers or blades in datacenter environments as well as cooler, quieter workstation designs. This is a critical factor for HPC environment.

The bottomline is Opteron is more scalable than Itanium in terms of speed. If we add more CPUs, the Opteron speed will increase as opposed to Itanium. To make things worse, the bandwidth between CPUs will be divided evenly.

These are distinctive features on AMD Opteron that made it suitable for SUN to bundle it for their server products. Although Intel is popular, for technical people, popularity is nothing. The technical side of it is more important and pricewise it is cheaper too.

ps : This article is not endorsed by AMD :-)

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Moving your mysql database to another hard disk

Recently, my server's only hard disk was almost full. I bought a new hard disk with bigger size and I decided to just add it as a second hard disk. Since I need to move it to the 2nd hard disk, I need to find a proper way to move the db with minimum downtime. So I googled around and found a solution.
First, I needed to format the 2nd hard disk and I chose xfs as the filesystem. I created 2 partitions using Linux's fdisk for this task. First partition is 10 GB and 2nd one is around 900 GB. That's approximately added up to 1 TB. Then I mounted the 2nd partition in current partition eg /media/hd2 as follows:
mount -t xfs /dev/sdb5 /media/hd2
where /dev/sdb5 is the partition and /media/hd2 is the mounting dir.
Stop mysql db before doing anything:
service mysql stop
Afterthat, I copied the entire db to newly mounted hard disk:
cp -rv /var/lib/mysql /media/hd2
It will take a while if you have huge databases.
Then, change the ownership of the dir to user and group of mysql:
chown -R mysql:…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy