Quote:
Your processor's clock speed is how fast your processer is.It sorts out all of your info and proccess it. It is messerd by Mhz or Ghz. ill give you an example. 2GHz to 3GHz is a 1000 Mhz increase sow its speed has increased by 1 Ghz.
Close, but not quite. M/G/T-FLOPS or M/G/T-IPS are measures of a processor's speed.
"In a computer, clock speed refers to the number of pulses per second generated by an oscillator that sets the tempo for the processor. Clock speed is usually measured in MHz (megahertz, or millions of pulses per second) or GHz (gigahertz, or billions of pulses per second)." - http://whatis.techtarget.com/definit...211799,00.html
CPUs with more advanced instruction sets (x86 is rather aenemic, not as bad as it has historically been, but still so) can perform more instruction per time, for example.
(VERY simplified)
CPU X has the following instructions: +1, -1
CPU Y has the following instructions: +1, +2,... +10,000, -1, -2, ... -10,000
CPU X has a clock speed of 10GHz
CPU Y has a clock speed of 1MHz
CPU X is 10,000 times faster, right?
Our program calls for a cycle of addition and then auditing with subtaction (to ensure a zero total)
10000 + 10000 = 20000
20000 + 10000 = 30000
30000 + 10000 = 40000
40000-(10000+10000+10000+10000) = 0
CPU X requires 110,000 cycles to perform this task
CPU Y requires 11 cycles to perform this task
Since CPU X is 10,000 times faster, the two chips work equally fast, CPU Y however will use much less power and subsequently generate less heat.
Quote:
Ram standes for (Random Assecible Memory) it is what programs use to run on. The more ram you have the smoother your programs wil run most likley. Ill give you an example. Windows Xp needs 128mb of ram to run properly.Sow if you dident have 128mb of ram Windows Xp might run slowly.
This is kinda sorta true, first it is Random Access Memory, and this is because the memory can be accessed asequentially. In reality you really don't need RAM, it just happens to be the crossover point of the cheapest/fastest way to handle subject memory.
Alternate methods of managing this memory are CPU cache (most CPUs have less than one meg of usable cache however). This is the fastest and most expensive method, which is why CPUs high in cache like Intel's Xeon CPUs work so well for servers that repeat the same tasks over and over. These tasks may be loaded into the cache, saving the system from having to look to the RAM. The other method is paging or as you in Linux land call it, the swap file. This is where data is written to a dedicated partition on the hard drive. This method is very cheap (since you more than likely have a little spare disk space and RAM costs money) and most operating systems require a paging file, just as they require RAM and CPU cache. Gotta be universal.
Quote:
I dount now any thing about bus speed
Bus speed is the speed at which data moves from one element of the system to another (from the CPU to the RAM, from the video card to the CPU, from the hard disc to the CPU, from the PCI card to the CPU, etc). This is measured in bits (how wide the pipe is) and clock speed, defined the same as above.
Quote:
I think 32bit and 64bit have some thing to do with how the cpu proccess data.
Sorta again, this is how wide the processor pipe is.
if CPU A is a one bit processor and CPU B is a two bit processor, processor B can move data through at twice the speed of CPU A. granted the actual data processing still deals with the CPU clock speed and instruction set, but still moving more data through is always a good thing.
And now... I'm missing ATHF...
cheers,
catch