Buying PC

[A-Man]

Not really and no.
It is the clock rate, but it doesn't really necessarily relate to instructions that can be executed per second.
First of all different instructions take different amounts of clock cycles, and second of all the amount of clock cycles a single instruction takes can vary from processor to processor.

Are you sure the clock rates don't relate to the numbers of instructions? I haven't got my information from anywhere directly; I just noticed a property of ASM instructions in multiple documentations and articles called "cycles". For instance, take a looks at this. The "MOV address1, address2" ASM instruction requires 2 cycles to complete. Doesn't this mean that a processor with 2.0 GHz could complete 1*10^9 "MOV address1, address2" instructions per a second? If so, then isn't this direct evidence that the clock speed, or its' frequency to be precise, what mostly makes a processor faster at processing processes?

Not entirely true. For one thing the number of cores doesn't really have anything to do with the amount of threads a process can run. It is entirely possible to have a multiple threads run on the same core. That said a well-written demanding program, will use multiple cores for its threads, also a game can easily (and will often) split its workload into multiple cores. That includes splitting the logic.

Definitely one can do as much threads as he likes, but they would only cause the increase in performance if each is run independently in one core. As far as I know, if a program uses more threads than the cores available, then the CPU would just run the different threads as if they were separate processes in the same core. This shouldn't cause any increase in performance, but further worsens it with the extra semaphores and syncronization stuff.

Seems right. I want to point out that there are different kinds of cache though. Namely L1, L2 and L3 though L1 and L2 is mostly constant across modern CPUs.

Sounds interesting. Just to make sure I got the idea of the cache memory right; I assume this is where the variables and stuff you don't store in a heap go? (I remember when I first started C++, my program threw a Buffer Overflow because of a non-new allocated array that slightly began to exceed 4MBs in size).


Edit:
@Labeeb: Are you seriously ready to pay 500$ for a graphics card? You can get 2 decent laptops for that price.