I am no expert, but it looks like my CPU is not maxing out at 100%, and that there is a lot of disc I/O going on.Quote from Tums:
What do you think? ;-)
How would you read the graphs?
However, take into consideration that in order to merely *run* Blocks on my machine, I had to slim Blocks down quite a bit, disable a lot of features I would like to use, and lessen the amount of data being calculated substantially from what I would ideally want to.
In other words, my system used to just hang when running Blocks until I "optimized" it for my slow, old system.
Not sure how this relates to the question at hand. Perhaps throwing money at the CPUs is not the answer? Perhaps the machine would be happy running on a single quad-core, or dual dual-cores, or even a single dual-core, and the real bottleneck is memory speed? Or memory capacity? Or hard drive speed? Or something else? I need to talk to the developers.
What do you make of this Tums? How do you read it?
My current system is actually a DAW I built 5 or 6 years back with the help of folks over at the DigiDesign forums.