I am a little confused. I have a device that is setup with an on/off switch that is supposed to disable the cpu when off. This seems to work. If I load a bunch of these (32 for example) and I turn them off I save about 10% on cpu usage over when they are on. The odd thing is that if I turn 1 on, it consumes the same amount as if I turn them all on.
Anyone know why this would be?
CPU usage
Re: CPU usage
dont trust the SISSDEM
good vibes dualcore and wannabes
edit:
imagin CPU0 and CPU1 are parents;
sissdemX.dev their child asking "can you play with me N O W??"
about every 100ms;
---
whats the algo behind your measurement?
peakholdvibes?
good vibes dualcore and wannabes
edit:
imagin CPU0 and CPU1 are parents;
sissdemX.dev their child asking "can you play with me N O W??"
about every 100ms;
---
whats the algo behind your measurement?
peakholdvibes?
- Attachments
-
- SissdemX.zip
- (20.62 KiB) Downloaded 200 times
Re: CPU usage
I have no idea what this is, but anything from my Brotha' in Austria who mourns fallen heroes like Zawinul ( R.I.P.) is definately something to be thankful of.
I hear there's an SDK on the skillet............I pray that you are around when these days come.
Thanks Bro...
I hear there's an SDK on the skillet............I pray that you are around when these days come.
Thanks Bro...
Re: CPU usage
it displays the cpuload in % of cpu0 and cpu1 in a 100ms updaterate_
move some windows to see the cpus working_
open windowsexplorer -> open a folder with some pics in and see what the sissdem (system) does;
i use similar to troubleshoot for prozesses that create high cpuloadspikes;
it should explain why you cant see each spike created in for example the taskmanager cpuloaddisplay_
hope it helps_
good vibes
move some windows to see the cpus working_
open windowsexplorer -> open a folder with some pics in and see what the sissdem (system) does;
i use similar to troubleshoot for prozesses that create high cpuloadspikes;
it should explain why you cant see each spike created in for example the taskmanager cpuloaddisplay_
hope it helps_
good vibes
Re: CPU usage
Wow, you completely lost me. I guess it's my fault. I am talking about dsp load, not cpu load. I am going by the dsp meter.
I would load a bunch of channel strilps I created. They should reduce dps load when i mute. But with 25 loaded, the meter did not change until all 25 were muted.
I would load a bunch of channel strilps I created. They should reduce dps load when i mute. But with 25 loaded, the meter did not change until all 25 were muted.
mark winger
Re: CPU usage
Try this when all loaded/unmuted : Note exact position of DSP meter. Mute one strip then wait several seconds. If DSP meter has not gone down, save project, close Scope, reopen, reload project. Has DSP meter gone down now ?
Dunno what this proves, except maybe if DSP meter has not gone down may be a problem in the way you built the device in that the strips aren't totally seperate instances but use some common instances of Scope atom(s) ?
If it has gone down, more likely issue on the Scope side rather than your device.
Another thing to try - if you save/load project while all strips muted, then unmute one strip then another (leaving a couple of seconds in between), does DSP meter increment in small even steps as you go ?
Dunno what this proves, except maybe if DSP meter has not gone down may be a problem in the way you built the device in that the strips aren't totally seperate instances but use some common instances of Scope atom(s) ?
If it has gone down, more likely issue on the Scope side rather than your device.
Another thing to try - if you save/load project while all strips muted, then unmute one strip then another (leaving a couple of seconds in between), does DSP meter increment in small even steps as you go ?
Re: CPU usage
look at the mdl attributes there you see whats up;
good vibes
good vibes
Re: CPU usage
Have been away for a while. Will do what Dante suggests.
tgsts said "look at the mdl attributes there you see whats up;".
I don't understand. What attributes are you talking about?
tgsts said "look at the mdl attributes there you see whats up;".
I don't understand. What attributes are you talking about?
mark winger
Re: CPU usage
winger,
the problem is you posted your question in the Development section. things discussed here are mostly about sdk. ergo, you need sdk to look at the mdl attributes of a device or plugin However, I think it's just a missunderstanding between you and tgstgs Hope this helps, not with your question, but for communication...
the problem is you posted your question in the Development section. things discussed here are mostly about sdk. ergo, you need sdk to look at the mdl attributes of a device or plugin However, I think it's just a missunderstanding between you and tgstgs Hope this helps, not with your question, but for communication...
Re: CPU usage
a dsp is a cpu right_
but it is a special cpu;
in scope code may be executed on dsp(s) as well as on host cpu(s) or on both;
sissdemx is an example of code being executed on host cpu only;
for me its one of the main advatages of scope to be able to choose and use whatever is best for;
so i call the dsp(s) dsp and the host cpu(s) cpu;
anyway . .
put a dynvoicesofparent inside the module;
if you set its voicespad to 0 you take a module and all its childs off dsp;
right mouseclick on the module to open moduleattributes;
the voices should be 0;
if they are still 1 or more it is still on dsp and you had to check your circuit;
if a mdl code (or parts of it) run on cpu you take off cpu as well;
but have in mind that it is not completely taken off dsp or cpu;
if so it would disapear from your project;
sorry this is the most details i can give in public;
for more ask sc_
good vibes
but it is a special cpu;
in scope code may be executed on dsp(s) as well as on host cpu(s) or on both;
sissdemx is an example of code being executed on host cpu only;
for me its one of the main advatages of scope to be able to choose and use whatever is best for;
so i call the dsp(s) dsp and the host cpu(s) cpu;
anyway . .
put a dynvoicesofparent inside the module;
if you set its voicespad to 0 you take a module and all its childs off dsp;
right mouseclick on the module to open moduleattributes;
the voices should be 0;
if they are still 1 or more it is still on dsp and you had to check your circuit;
if a mdl code (or parts of it) run on cpu you take off cpu as well;
but have in mind that it is not completely taken off dsp or cpu;
if so it would disapear from your project;
sorry this is the most details i can give in public;
for more ask sc_
good vibes