[Csnd] csound-double Intel-mac OSX render-to-disk CPU question
Date | 2009-05-20 02:51 |
From | peiman khosravi |
Subject | [Csnd] csound-double Intel-mac OSX render-to-disk CPU question |
Dear all, I am using csound double to render to disk a very complex CSD that uses PVS opcodes (including the highly CPU intensive pvsblur) with FFTsize=2048, overlap size of FFT/16 or less (e.g. 128), window-size of FFT*8, ksmps=1 and 96khz sr, also using flag -3 (for 24 bit sample output). These settings would naturally be impossible to run in real-time considering the nature of my csd.
So I am not surprised that at the end of the non-real-time performance the terminal prints out this: Elapsed time at end of performance: real: 135.728s, CPU: 133.630s
Is this just theoretical? How can the CPU go over 100% without csound freezing? I admit I don't understand what this means exactly. In short is this a problem or can it cause problems? (apart from the computer fan spinning like crazy and me having to finish a cup of coffee for each render!).
Also would it make sense that for some reason audio signal of 0 sample value seems to create some sort of CPU spike in real-time performance? Many Thanks Peiman
|
Date | 2009-05-20 03:03 |
From | Mike Moser-Booth |
Subject | [Csnd] Re: csound-double Intel-mac OSX render-to-disk CPU question |
Hello, I think the CPU spike has something to do with the fact that Intel processors actually have to strain harder when dealing with very small values than with large ones. As for the elapsed time, I never really paid attention to it, but I always just assumed the "s" stood for seconds. But I couldn't finish a cup of coffee in 133 seconds! So maybe I'm wrong on that. .mmb peiman khosravi wrote: > Dear all, > > I am using csound double to render to disk a very complex CSD that > uses PVS opcodes (including the highly CPU intensive pvsblur) with > FFTsize=2048, overlap size of FFT/16 or less (e.g. 128), window-size > of FFT*8, ksmps=1 and 96khz sr, also using flag -3 (for 24 bit sample > output). These settings would naturally be impossible to run in > real-time considering the nature of my csd. > > So I am not surprised that at the end of the non-real-time performance > the terminal prints out this: > > Elapsed time at end of performance: real: 135.728s, CPU: 133.630s > > Is this just theoretical? How can the CPU go over 100% without csound > freezing? I admit I don't understand what this means exactly. In short > is this a problem or can it cause problems? (apart from the computer > fan spinning like crazy and me having to finish a cup of coffee for > each render!). > > Also would it make sense that for some reason audio signal of 0 sample > value seems to create some sort of CPU spike in real-time performance? > > Many Thanks > Peiman |
Date | 2009-05-20 11:03 |
From | peiman khosravi |
Subject | [Csnd] Re: Re: csound-double Intel-mac OSX render-to-disk CPU question |
Hi Mike, Thanks for the clarification. In truth I'm batch processing so multiply this by 20! So CPU: 133.630s is in seconds and not percentage? That makes sense now! Cheers Peiman
2009/5/20 Mike Moser-Booth <mmoserbooth@gmail.com> Hello, |
Date | 2009-05-20 11:12 |
From | Victor.Lazzarini@nuim.ie |
Subject | [Csnd] Re: Re: Re: csound-double Intel-mac OSX render-to-disk CPU question |
Attachments | None None |
Date | 2009-05-20 11:48 |
From | peiman khosravi |
Subject | [Csnd] Re: Re: Re: Re: csound-double Intel-mac OSX render-to-disk CPU question |
Thanks very much for the explanation Victor. Now I understand :-) Best Peiman
2009/5/20 <Victor.Lazzarini@nuim.ie> What you get reported is basically the CPU time it takes for the processor to |
Date | 2009-05-20 16:50 |
From | Michael Gogins |
Subject | [Csnd] Re: csound-double Intel-mac OSX render-to-disk CPU question |
The CPU of course cannot go over 100%. CPU time is not real time. What you are ultimately interested in real time or wall clock time, the time that you yourself experience. The CPU is not necessarily running at every point of wall clock time. If the computer is set up right, it of course will devote itself to 100% of CPU time to computing an intense job. This is what we want, with just enough power left over to handle interruptions. Floating point numbers very close to 0 can indeed cause performance problems on some computers. This is the dreaded "denormal" problem and you can google this term to learn more. Hope this helps, Mike On 5/19/09, peiman khosravi |
Date | 2009-05-20 17:10 |
From | peiman khosravi |
Subject | [Csnd] Re: Re: csound-double Intel-mac OSX render-to-disk CPU question |
ahhh great! I just found out that there is even a denorm opcode! Thanks Michael Peiman
2009/5/20 Michael Gogins <michael.gogins@gmail.com> The CPU of course cannot go over 100%. CPU time is not real time. What |