Calculating Overhead with Syphon

Home Forums Syphon Syphon Implementations – User Calculating Overhead with Syphon

This topic contains 2 replies, has 2 voices, and was last updated by  Casey_Scalf 4 months, 3 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #59282

    Casey_Scalf
    Participant

    I love and use syphon frequently but do not know much about calculating the computational “overhead” of where and when to use it.

    I have been using it in Quartz Composer but more recently in Processing.

    My question is this: how can I calculate how computationally taxing a certain syphon use case will be?

    For instance. Is it more taxing with color? What about if I use more than 1 syphon instance in a program? How about resolution? Frame rate?

    How can I begin to calculate these taxes without taking the time to build out the program and see for myself.

    Is there any rough math? References? Maybe general rules to stay away from (i.e. large resolutions, etc).

    This way I could avoid pitfalls before coding and structure the program best before developing.

    Thank you so much for any tips or leads!

    #59285

    bangnoise
    Keymaster

    Syphon shouldn’t be adding significant overhead – the parts of the process to do with generating and affecting your content are likely to be the drain on resources. Only start to worry about it if you are starting to hit limits (eg dropped frames). In that case, try each part of your pipeline independently to identify the part that is struggling. If you still see problems without Syphon being involved, then Syphon isn’t the problem.

    There is no simple maths you can do. Syphon treats all content the same – the only significant hit Syphon will cause is when you resize the Syphon frames, in which case the underlying surface is rebuilt. Otherwise the only limitation is, as with any graphics work, that the more pixels you are working with the more work needs to be done.

    #59286

    Casey_Scalf
    Participant

    Well that sounds like good news.

    I was hoping that it would be lightweight enough. Most of my image pipelines stay at the same resolution all the way through such as 640 x 480.

    I have found some trouble using Processing and Syphon. I have found that sometimes using Syphon in the code, as illustrated in the examples – using a PGraphics object – the sketch runs significantly slower.

    However, when I use something like “Syphoner” and removing the Syphon code in Processing it runs much faster.

    This prompted me to investigate and sparked the initial post here.

    I will prepare a bit of sketch code to show this.

    Thank you,

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.