[PD] optimizing big patches
ludwig.maes at gmail.com
Mon Jan 10 10:03:43 CET 2011
I always felt message passing was unnecessarily expensive but I didnt
realise message passing was that expensive!
I seriously think it would be good to have a pd front end for gcc, a
few of us should take the time to learn GIMPLE and implement a
"compile" menu item to compile patches/subpatches.
2011/1/10 Mathieu Bouchard <matju at artengine.ca>:
> On Sun, 9 Jan 2011, Pedro Lopes wrote:
>> i Guess the question could go a bit further, how can we devise a profiling
>> system for a dataflow programming environment?
> I made two or three of those... GridFlow had several incarnations of such a
> thing but it only worked for GridFlow's own objects.
> Then I made one for the whole of Pd, and it's somewhere in the DesireData
> branch, but it caused occasional crashes for mysterious reasons, and no-one
> else looked at the code.
> Here's a screenshot of the latter :
> You see that [cos] is over twice slower than [*] but [t f f] minus those two
> is also a lot, but that's the cost of message-passing, because [t f f]
> doesn't do any processing. And so on... the top number is the total time for
> the first message to "return" (every message-passing down a wire is
> accompanied later by an opposite movement once the job is done... that's
> "the stack").
> GridFlow's profiler instead had a menu in Pd's main window which had a
> "reset" and a "dump" and the latter would print non-cumulative measurements
> (i.e. it doesn't include time in objects sent to) in the console (or in the
> terminal back when there wasn't a console) sorted by decreasing importance.
> Ideally we would have both cumulative and non-cumulative figures, because
> neither is nearly as useful as both together.
> | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
More information about the Pd-list