nawwww, that's the cpu usage... we were talking about multi-core parallel processingpopmoney wrote:Using the 8.5 beta here and a few times I looked at the cpu meter I was surprised to see it at 35% and not up around 50/55 like it had been in FL8
Does FL Studio support multi core ?
-
- KVRist
- 295 posts since 23 May, 2009
-
- KVRist
- 479 posts since 27 Apr, 2005 from Ireland
You've lost me.I'm in the dark re the nuts and bolts of the technologyArkadey wrote:nawwww, that's the cpu usage... we were talking about multi-core parallel processingpopmoney wrote:Using the 8.5 beta here and a few times I looked at the cpu meter I was surprised to see it at 35% and not up around 50/55 like it had been in FL8
So if I'm using FL how would improvements in multicore processing show themselves.
-
- KVRian
- 1270 posts since 9 Sep, 2005 from Oulu, Finland
Say, if you have quad core machine and you can clearly make FL use more than 25% (say at least 50%) CPU as shown in Task Manager and there are no audio playback problems, then it likely has incorporated proper multithreading support. (The reasoning behind this is that an app doing it's main work in only thread could use at most 25% CPU in a quad core machine, 50% in a dual core, 12.5% in an octo core etc...It's all of course more complex, maybe there is a GUI thread too that can use lots of CPU resources etc...)popmoney wrote:You've lost me.I'm in the dark re the nuts and bolts of the technologyArkadey wrote:nawwww, that's the cpu usage... we were talking about multi-core parallel processingpopmoney wrote:Using the 8.5 beta here and a few times I looked at the cpu meter I was surprised to see it at 35% and not up around 50/55 like it had been in FL8![]()
So if I'm using FL how would improvements in multicore processing show themselves.
-
- KVRist
- 169 posts since 2 May, 2003 from Home, sweet home.
There's a simpler approach to cpu usage:Xenakios wrote: Say, if you have quad core machine and you can clearly make FL use more than 25% (say at least 50%) CPU as shown in Task Manager and there are no audio playback problems, then it likely has incorporated proper multithreading support. (The reasoning behind this is that an app doing it's main work in only thread could use at most 25% CPU in a quad core machine, 50% in a dual core, 12.5% in an octo core etc...It's all of course more complex, maybe there is a GUI thread too that can use lots of CPU resources etc...)
Don't worry about it,
as long as it is not a problem.
I use FL8 on a 2.66 GHz dual core Pentium PC
and i don't care about cpu usage
simply because it never stopped me
from doing what i wanted.
Who cares if all cores are used
when you got a great groove going
and you get no clicks or dropouts?
Worry about the music, not the cpu strain ...
-
- KVRian
- 1270 posts since 9 Sep, 2005 from Oulu, Finland
If an app you are using a lot isn't multithreaded properly and you have also invested into a multicore setup, you have essentially wasted money as all the CPU resources are not utilized. Performance in CPUs is these days coming mostly from the multiple cores, not raw clock speed, and that situation doesn't seem to be changing in the immediate future much.Sotiris wrote:
Who cares if all cores are used
when you got a great groove going
and you get no clicks or dropouts?
Worry about the music, not the cpu strain ...
Responsibility of high performance in applications has been shifted from the CPU manufacturers to the application program developers. If that is a good thing or not, is of course debatable. I am personally a bit pessimistic about the situation. Multithreaded programming is not easy. (But it's unforgivable to not at least try...
-
- KVRian
- Topic Starter
- 1161 posts since 24 Dec, 2004 from Adelaide, South Australia
They're not going to do that because of a cohort of lazy developers now are they?Xenakios wrote:If an app you are using a lot isn't multithreaded properly and you have also invested into a multicore setup, you have essentially wasted money as all the CPU resources are not utilized. Performance in CPUs is these days coming mostly from the multiple cores, not raw clock speed, and that situation doesn't seem to be changing in the immediate future much.Sotiris wrote:
Who cares if all cores are used
when you got a great groove going
and you get no clicks or dropouts?
Worry about the music, not the cpu strain ...
Responsibility of high performance in applications has been shifted from the CPU manufacturers to the application program developers. If that is a good thing or not, is of course debatable. I am personally a bit pessimistic about the situation. Multithreaded programming is not easy. (But it's unforgivable to not at least try...) But there's tons of old code designed around single threaded execution that might never get rewritten for multithreaded use, thus the performance benefits of today's and future's multicore systems will never be realized. IMHO CPU manufacturers should maybe go back to the gigaherz per core competition...
Besides which, there is a ceiling on the speed of one core. Unless you're willing to ship out super fast cores with liquid cooling to consumers or wait until they reach a super small nano meter manufactuiring process, then multi core makes more sense, is more powerful and makes multiple operating systems running simultaneously possible at some point in the future, The benefits of multi core far outweigh the disadvatntages and in a decade or less, it will be so commonplace, along with 64 bit, that everyone will think single core computers vintage.
Times change and so do CPUs. Multi core is the way of the future, just like 64 bit.
Mixcraft 8 Recording Studio : Reason 10
-
- KVRist
- 156 posts since 13 Aug, 2005
So... I'm using FLStudio 9 with a i7-860 quad core processor. When rendering an audio file, the Performance tab under Task Manager shows CPU usage to be ~50%. Of the 8 threads separately shown in the CPU Usage History area, 7 seem to be used for around 50%. Why not full power?
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
Because it isn't needed?.Aukikco wrote:So... I'm using FLStudio 9 with a i7-860 quad core processor. When rendering an audio file, the Performance tab under Task Manager shows CPU usage to be ~50%. Of the 8 threads separately shown in the CPU Usage History area, 7 seem to be used for around 50%. Why not full power?
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRist
- 156 posts since 13 Aug, 2005
How come? I'd appreciate faster rendering. Could you open this up a lil' bit?standalone wrote: Because it isn't needed?.
-
- KVRAF
- 4222 posts since 23 Feb, 2004 from Tucson Arizona USA
It can be worse than that -- multiple cores can be a liability. We have an industrial application that performs terribly on a multi-processor multi-core system. In order to get acceptable performance from it we must run it on a single processor box and disable 3 out of 4 cores.Xenakios wrote:
If an app you are using a lot isn't multithreaded properly and you have also invested into a multicore setup, you have essentially wasted money as all the CPU resources are not utilized.
- KVRian
- 1052 posts since 2 Dec, 2010 from Belgium, EU.
We get a lot of questions about this. Here's something I wrote for the manual...
NOTE: If you open the Windows Task Manager and examine the number of cores used and their relative loading, this is under the control of Windows. This may come as a surprise since marketing departments make a lot of noise about their multi-threading 'optimizations'. Really, all programs do is publish at least as many threads (independent processes), as there are cores available. FL Studio does that, but, it's the Windows Scheduler that is largely responsible for the core assignment. To complicate matters even single-threaded application may use several cores if Windows decides to flip core assignments at some point, and it often does. So what matters? - If you are testing and comparing CPU loads it is the number of plugins and or effects that can be processed without buffer underruns and the FL Studio internal CPU meter. This is the real-world measure you should use. Don't obsess about how cores are used, particularly at low CPU levels, since the Scheduler will even out this distribution as CPU load approaches 100%. Registered users can see some graphs testing FL Studio core usage here - http://forum.image-line.com/viewtopic.p ... 764#370764
...so in this graph (on a i7-860 quad core with HT) I added plugins to FL Studio at a constant rate and recorded the CPU load until underruns occurred.

Regards Scott
NOTE: If you open the Windows Task Manager and examine the number of cores used and their relative loading, this is under the control of Windows. This may come as a surprise since marketing departments make a lot of noise about their multi-threading 'optimizations'. Really, all programs do is publish at least as many threads (independent processes), as there are cores available. FL Studio does that, but, it's the Windows Scheduler that is largely responsible for the core assignment. To complicate matters even single-threaded application may use several cores if Windows decides to flip core assignments at some point, and it often does. So what matters? - If you are testing and comparing CPU loads it is the number of plugins and or effects that can be processed without buffer underruns and the FL Studio internal CPU meter. This is the real-world measure you should use. Don't obsess about how cores are used, particularly at low CPU levels, since the Scheduler will even out this distribution as CPU load approaches 100%. Registered users can see some graphs testing FL Studio core usage here - http://forum.image-line.com/viewtopic.p ... 764#370764
...so in this graph (on a i7-860 quad core with HT) I added plugins to FL Studio at a constant rate and recorded the CPU load until underruns occurred.

Regards Scott