---

Question 1:
What is a Floating Point Cacluation (Spelling)

---

A floating point calculation involves noninteger numbers. Multiplying 2 * 5 is integer multiplication, but something like 3.14159 * 5 is floating point.

---

Question 2:
What exactly is a Thread

Question 3:
What is a Handle

---

Not exactly sure either.

---

Question 4:
What is Kernel Memory

---

I am guessing this is how much of your RAM is actually occupied by the operating system itself.

---

Question 5:
What is Commit Charge

---

"In the Windows operating system, the name for the amount of physical memory (RAM) and virtual memory that is allocated to all running programs, or applications, and the operating system itself."

- Stolen from Wikipedia.

---

Question 6:
What does the show Kernal Times in the Task Manager show exactly

---

As best as I can gather it's how much of your CPU is being used directly by the operating system.

---

Question 7:
What is PF Usage thing in the Task Manager for

---

From the initials I would say Pagefile usage, and presumably it's just what it means - how much of the page file on your hard drive is actually being used up.

---

Question 8:
What is the diffrence between a L2 Cache and a L1 Cache and what do they do

---

In general those caches are for your CPU. Because modern processors are so fast at executing instructions, and a fair number might be loops that are re-executed several times, they will "pre-fetch" an 8K, 16K, or even a 1 meg (if the cache is that large) block of instructions into the much-faster cache RAM (regular RAM is actually slow by CPU speed standards), and then execute instructions from the cache.

L1 cache is usually the smallest, and fastest cache, and is almost always directly on-die.

L2 cache in the past has been "off-die", but has in recent years been put on-die with the CPU. It's slower than L1 cache, but still faster than system RAM so it's where the bulk of the prefetched instructions go.

http://en.wikipedia.org/wiki/CPU_cache <-- Look there for more info.

a thread is a series of instructions which should really be described as program tasks, hence the term multi-threading which refers to a program running multiple tasks (ie threads) simultaneously. Unlike processes which they superficially resemble, threads contain less state information therefore can operate rather more efficiently although they are completely dependent on their host executable. Intel's HT technology should really be described as simultaneous multi-threading.

a handle is a call on memory resources by a program usually to another to another program, it was a major elemnt of memeory management in DOS, OS/2 and early Windows but it's used a lot less now because it's *bloaty* code and prone to be buggy - many databases used handles/pointers in the past and were notorious for *leaking* memory.

kernel memory is the amount of RAM the o/s kernel threads use as distinct from user application threads. It is very important to ensure your system is managing memory effectively as a runaway process can reduce the amount of RAM for the kernel to not very much at all thus causing your system to be very poorly.

what do you want to know all this stuff or anyway? if you aren't going to do computer science you'll never need to know.

I was just curious

thx