Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running test pipelines and my charts look nothing like the examples ?? #74

Open
js1972 opened this issue Jun 1, 2020 · 1 comment
Open
Assignees
Labels

Comments

@js1972
Copy link

js1972 commented Jun 1, 2020

Hi, I'm trying to test gst-shark on an nvidia jetson nano by going through the sample tests provided for each tracer here: https://developer.ridgerun.com/wiki/index.php?title=GstShark_-_Processing_Time_tracer

I'm finding that my charts look nothing like those you show... I've installed from master - should I be looking at a different branch?

I have attached an example of the proctime tracer graph - you can see its totally different to the graph shown on your website (link above)

tracer_proctime.pdf

@michaelgruner michaelgruner self-assigned this Jul 3, 2020
@michaelgruner
Copy link
Collaborator

Hi @js1972 sorry for the slow response. Indeed the plot in the wiki is way to smooth compare to what I also get. I updated the wiki with the plot I got. It matches the expected behavior but it's more realistic.

Now, looking at your graph, it looks as if the pipeline would've gotten stuck in one of the branches and the queue started accumulating buffers. Do you get this result consistently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants