199,020 users have contributed to 43,150 threads and 258,877 posts.
In the past 24 hours, we have 7 new thread(s), 15 new post(s) and 57 new user(s).
Performance meter is always in real-time, while the Activity Monitor takes an average value.
I would say that something is wrong, either the design or the implementation. If your meter constantly shows 10% and the Task Manager constantly shows 2%, there can't be a difference just based on real time vs average value. And even if all numbers actually are correct - in what way does your 10% value give me any usable information for a process that have an average load of 2% on my system?
I have measured the CPU load for the VEP process over time and have attached the graph. During this period (1.5 minute) my impression from the performance meter in VEP was that there were about 10% constant load. According to the performance monitor, the CPU load from the VEP process averaged around 4% (the scale is x10 in the graph) and only once managed to get above 10%.
The thing I'm getting at here is that even if the numbers technically would be correct (which I honestly doubt), the implementation gives me the wrong impression. As I said - during this period when I measured the CPU load using Performance Monitor, my impression from the CPU meter in VEP was that there were a pretty stable load of about 10%.
Maybe having a CPU meter going all over the place in real time isn't the best way to give the user a usable estimation of the CPU load?
I question how you are using Task Manager to measure CPU utilization. on my mac, I can run VePro with a small test, Vepro shows 6% and my Cpu utilization meter for the whole computer also shows 6%. If you are trying to measure just one particular process with Task Manager you might not be getting the whole story. I'm not that familiar with the Windows version of Vepro but its possible that multiple processes are involved that need to be measured by Task Manager. But I think if you just monitor the overall CPU utilization of the machine it should be pretty close to what VePro is saying also.
Remember also that cpu utilization measurements are always an average, but different tools may use a different time period to measure that average. A shorter time period would result in a curvier line.
So on a Mac it obviously works. On Windows it don't. When it comes to reports on CPU utilization I trust the Operating System more than VEP, the OS is after all in control of the whole situation.
And it isn't about measuring the correct processes. While VEP is constantly reporting around 10-11% for a single instance, the complete load on my CPU from all running processes including the OS itself i pretty stable at 7% (and I have a lot of things running in that machine...)
Believe me - on Windows VEP is reporting an incorrect CPU load. No matter what other tools I use for CPU performance reports (built in or 3rd party) they show way lower CPU load than what VEP does.
As I said, in task manager you are trying to measure the VePro process itself and there may be other hidden CPU activity related to VePro at work in the kernel or other processes which you are not measuring with Task Manager in that case.
Change your Task Manager configuration to measure the entire overall system CPU utilization, and I suspect that it will be similar to what you see in the Vepro cpu report...as long as you don't have anything else big running on the machine at the time.
Change your Task Manager configuration to measure the entire overall system CPU utilization...
Windows Task Manager is built to measure the entire overall system CPU utilization, it can't be configured. The entire overall system CPU utilization is quite a bit lower than what VEP reports to use all by its own. But I give up. If you do not think it is a problem that your program shows the wrong CPU load, then I should not push the question anymore.
...No I don't particularly think its a problem...
I appreciate that clarification.
You list this as a new feature and as a selling point for VEP 7. In the promotional video for the feature (introduced with "control is an important factor"), the combined "real time CPU load" from the instances averages around 150% and sometimes goes above 200%. For me, it is extremely obvious that this is not correct.
I have been using the trial version of VEP 7 for some time and was about to purchase a couple of licenses now in the June promotional prices. I'm glad that I in time got to realize that support of this product is more interested in finding excuses than finding the cause of the problem.
1. The VEPro CPU meter measures real-time thread use only. If you are running at a buiffer size of 256 samples, and samplerate of 44100 Hz, every buffer has to be processed within 5.8ms. If VEPro manages to process that buffer within 0.58ms, the real-time CPU usage would be 10%.
2. Plug-ins may spawn threads that process things in the background. This will affect the process/system CPU load, but may not show up in the real-time CPU meter. There is no way for VEPro to know about these background threads.
1. The VEPro CPU meter measures real-time thread use only. If you are running at a buiffer size of 256 samples, and samplerate of 44100 Hz, every buffer has to be processed within 5.8ms. If VEPro manages to process that buffer within 0.58ms, the real-time CPU usage would be 10%.
Martin thanks for that explanation! In many ways that is much better metric than the actual CPU utilization. Because it will show on a scale of 0-100% how close you are to drop outs...regardless of what the CPU utilization is actually doing on the system.
Do I understand that right?
