You couldn't reasonably tag every object with a cost because that might change for many reasons, but you can know the load of an object or patch on your current CPU using the [cputime] object which shows a percentage scale. You can usually use it to work out the heavy offenders by "muting" DSP with [switch~] and seeing what is using up lots of cycles, but it's not really accurate benchmarking.
On Thu, 09 Nov 2006 00:34:16 -0500 Marius Schebella <[EMAIL PROTECTED]> wrote: > Hi, > for me that's a really important topic, I often run into problems with > slow machines not fast enough to play patches. > I wonder if it is possible to calculate something like flops/ FLOating > Point OPerations per object and have a list for all the pd objects. > it really would be great to know the benchmarks of different > hardwaresystems. > marius. > > _______________________________________________ > PD-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
