Note: A Duron processor has a smaller cache (hense a lower price) (probably why they are using that for their upgrade, cheaper for them)
What that means in a production environment, is that the processor cannot retain as much info as the Athlon cache resulting in increased harddrive access (HD access is much slower than accessing recent info from the onboard cache)
The processor may be faster, however your website is not number crunching (unless you run a DB). This means that you probably will see no evidence of an increase in speed at all.
Speed comes from fast drives, fast network cards, and a fast connection to the net.
Hope that helps some...
Thanks, I am using a web application server that is pretty CPU intensive, but also uses a lot of RAM.
Good info on the Athalon, I didn't know it has less cache.
If your app is using a lot of sytem resources then you will see a bit of a difference in terms of performance.
Sites that will not see much difference are sites using nothing more than static content. An http server uses very little in terms of ram or cpu. The increase you will see with plain html sites is very very minimal.
In your case you may notice an improvement.
My application is pretty CPU intensive, so it sounds like I will get a bump in performance in this upgrade.
Thanks for all your help.
After a little "negotiating" I got the following:
From: 2.13 Ghz AMD Athlon XP 2600+ -> 2.0Ghz AMD Athlon 64 3200+ 2.0 GHz
From: 1.5 GB DDR Ram -> 2.0GB DDR Ram
Everything else remained the same.
Since the whole AMD Athlon/Duron/64/XP/3200/2600 means nothing to me, could someone give me a clue as to what I upgraded to?
First thing - the Duron is not 2.8Ghz.
Forget the Hz bit, just look at the big number as this is the performance rating and can help to compare between chips and roughly between Intel and AMD.
Going from a 2600 to 3200 is roughly a 24% increase in CPU power. You should also experience a better bus speed and memory speed due to the better memory controller with these chips.
What you have now is a true 64 bit processor. You'll enjoy a much more faster and efficient processor as it is, but you gain even more if your O/S is the 64 bit version too.
Don't worry if it is not as you should see a good improvement over the old XP 2600 CPU.
They did say the needed to replace the motherboard as well, which I assume means different bus speeds which should help.
All in all it seems a bit faster now, but it is hard to tell. Looking at the server performance logs (sar) I find it is running about as much idle / working as before.
10:10:00 CPU %user %nice %system %iowait %idle
12:30:00 all 1.26 7.71 1.11 0.00 89.92
12:40:00 all 1.13 9.97 1.03 0.00 87.87
12:50:00 all 1.47 7.90 0.88 0.00 89.75
13:00:01 all 1.50 9.26 1.02 0.00 88.22
13:10:01 all 1.54 7.59 0.91 0.00 89.96
13:20:00 all 0.78 8.31 0.96 0.00 89.95
13:30:00 all 1.22 10.48 1.24 0.00 87.07
13:40:00 all 1.31 7.49 1.18 0.00 90.02
13:50:00 all 1.16 6.61 0.93 0.00 91.30
Average: all 1.45 7.28 0.95 0.00 90.32
Make sure they have done the change by checking your cpu info
or use one of the ready made php system info type scripts.
Don't forget that there is a heck of a lot of optimising you could be doing too.
I don't know how your server is setup but you should be able to fine tune various apps such as apache, mysql, php and the o/s etc.
Mostly these are memory tweaks so that less is used for unecessary things and more is used for caching.
But there are other things you can do such as removing the atime flag from the disk. This can be a big slow down as basically the disk has to write the time a file was read (every time a file is accessed it's time is stamped). You can also do things such as have log files on a seperate disk so that pages and data can be served from a slick disk whilst continual writes such as log files will be on a seperate dedicated disk and channel.
It all depends on your setup though.
Looks like it is the real deal.
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 15
model name : AMD Athlon(tm) 64 Processor 3200+
stepping : 0
cpu MHz : 2002.610
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
It runs pretty well and the application I use is not so common (Zope) so there are not a lot of optimization articles out there.
I guess I will wait till my traffic gets the server to like 50% utilization before really worrying about it, which might take me a year or so.