The difference is in the way the circuits on the motherboard are designed. Normally a desktop workload is no more than casual surfing, may be a bit of office suite tools or some developmental activity. All this pertaining to One physical user at a time. And not many services running on the system, which means the load on the system resources such as CPU, RAM & I/O is not very demanding. Hence the different interconnects between CPU, Mem & I/O are generally slower. Similarly the CPUs are generally designed to handle the compute requirements of a single user computing needs as mentioned above.
But a server is altogether different. It has to support multiple users. A server could be a web server, App server, DB server which require a lot of processes to be running in the background. This puts a lot of load on the CPU, RAM and I/O. Which means the bus(es) interconnecting the various peripherals have to be fast. There should be no bottlenecks. Also there should be provision to support multiple processors to cope with increasing work loads. Hence the bus(es) are designed to support this. Since the server is a critical, it needs certain Reliability. availability and serviceability (RAS) features, such as circuit redundancy built-in, remote management etc. All this require additional circuitary which needs to be incorporated on to the board.
On a broad level these are the fundamental technical differences between a desktop board and server board.
Hope that helps.
Server motherboards usually have dual sockets for processors.
-made only for servers and not for desktops.
-huge and never fit in computer cases.
-a lot of sockets for RAM and PCI-E
Desktop motherboards have only one socket for a processor.
-smaller than server ones and a lot cheaper.
-less sockets for RAM and PCI-E
About 200-300 bucks. Actually the difference is different chip. Most server motherboards use a XEON with is not used in desktop. Also they can support way more ram also. The price for it is about 2x or 3x a typical motherboard.
http://answers.yahoo.com/question/index?qid=20080208183342AAjfGbc
Friday, March 22, 2013
Tuesday, January 15, 2013
Remove wgasetup.exe Windows Genuine Advantage
Remove wgasetup.exe Windows Genuine Advantage
1) After windows starts, start > run > taskmgr
2) Click on the “processes” tab > find the “WGASetup.exe” process > right-click it > select “End Process Tree”.
3) start > run > control.exe schedtasks > Scheduled Tasks pops up.
4) Delete the “WGASetup” task.
5) Delete the following folder: “C:\WINDOWS\system32\KB905474″
6) Restart Windows.
1) After windows starts, start > run > taskmgr
2) Click on the “processes” tab > find the “WGASetup.exe” process > right-click it > select “End Process Tree”.
3) start > run > control.exe schedtasks > Scheduled Tasks pops up.
4) Delete the “WGASetup” task.
5) Delete the following folder: “C:\WINDOWS\system32\KB905474″
6) Restart Windows.
Tuesday, January 8, 2013
Audacity - is free, open source, cross-platform software for recording and editing audio sounds.
Audacity - is free, open source, cross-platform software for recording and editing audio sounds.
http://audacity.sourceforge.net/
http://audacity.sourceforge.net/
WinSplit Revolution
WinSplit Revolution is a small utility which allows you to easily organize your open windows by tiling, resizing and positioning them to make the best use of your desktop real estate.
Reference:
http://winsplit-revolution.com/
Reference:
http://winsplit-revolution.com/
Glances is a CLI curses based system monitoring tool for GNU/Linux and BSD OS.
Glances uses the PsUtil library to get information from your system.
It is developed in Python.
# cd /usr/ports/sysutils/py-glances
# make config-recursive
# make install clean
# rehash
# glances
Note: press "q" to quit.
http://nicolargo.github.com/glances/
It is developed in Python.
# cd /usr/ports/sysutils/py-glances
# make config-recursive
# make install clean
# rehash
# glances
Note: press "q" to quit.
http://nicolargo.github.com/glances/
Use lockf to prevent running multiple rsync processes
Use lockf to ensure only one instance of rsync is running at a time.
Reference:
http://blog.ijun.org/2010/02/rsync-synchronizing-two-file-trees_19.html
#!/bin/sh
runRsync () {
mode=${1}
lockFile=/tmp/test.lock
runCount=0
runMax=5
date "+rsync update starts at %Y-%m-%d %H:%M:%S"
while [ $runCount -lt $runMax ]; do
### program to execute.
if [ $mode = "PULLING" ]; then
lockf -t 0 ${lockFile} /usr/local/bin/rsync -avu --ipv4 --stats --safe-links --password-file=/usr/local/etc/rsyncd.passwd_rsyncbot rsyncbot@1.2.3.4::mybackup /home/srv/mybackup/
elif [ $mode = "PUSHING" ]; then
lockf -t 0 ${lockFile} /usr/local/bin/rsync -avu --ipv4 --stats --safe-links --password-file=/usr/local/etc/rsyncd.passwd_rsyncbot /home/srv/mybackup/ rsyncbot@1.2.3.4::mybackup
fi
### checking the exit status of the previous command.
if [ $? -eq 0 ]; then
break
fi
runCount=`expr $runCount + 1`
if [ $runCount -eq $runMax ]; then
break
fi
### retry after ten seconds.
sleep 10
done;
date "+rsync update ends at %Y-%m-%d %H:%M:%S"
}
#umask 27
### pulling from remote files to local
runRsync "PULLING"
### pushing from local files to remote
runRsync "PUSHING"
echo '[DONE]'
Reference:
http://blog.ijun.org/2010/02/rsync-synchronizing-two-file-trees_19.html
xz is a lossless data compression program and file format
xz is a lossless data compression program and file format which incorporates the LZMA2 compression algorithm.
xz is essentially a stripped down version of the 7-Zip program, which uses its own file format rather than the .7z format used by 7-Zip which lacks support for Unix-like file system metadata.[2]
Compress the file foo into foo.xz using the default compression level (-6):
# xz -zk foo
Decompress bar.xz into bar and don't remove bar.xz after decompression:
# xz -dk bar.xz
Using xz with tar (compress):
# tar Jcvf foo.tar.xz /home/backup
Using xz with tar (decompress):
# tar Jxvf foo.tar.xz
Reference:
http://en.wikipedia.org/wiki/Xz
xz is essentially a stripped down version of the 7-Zip program, which uses its own file format rather than the .7z format used by 7-Zip which lacks support for Unix-like file system metadata.[2]
Compress the file foo into foo.xz using the default compression level (-6):
# xz -zk foo
Decompress bar.xz into bar and don't remove bar.xz after decompression:
# xz -dk bar.xz
Using xz with tar (compress):
# tar Jcvf foo.tar.xz /home/backup
Using xz with tar (decompress):
# tar Jxvf foo.tar.xz
Reference:
http://en.wikipedia.org/wiki/Xz
Subscribe to:
Posts (Atom)