Marcus Asteborg

To avoid underutilization, (worse quality than libwebrtc) maybe step one could just be to use rtp header in the estimate and then remove the rtp overhead in the return bwe...

Returning the full "estimated bitrate" and then a way to get a rough estimate or average rtp overhead per stream is my vote. One could always return the full estimated...

So if an agreement is that str0m should generate the link bitrate and not media, then it's more of a question how to report the rtp overhead. The rtp header...

Ok, that's bad. What GPU and and how much memory do you have, roughly how many pictures did you process until you hit it? I will try to reproduce it...

Ok I managed to reproduce, if to many requests comes in it will overload it. So multiple things I need to look into, - stop leaving unwraps - investigate scheduling...

So good news is that it's not a memory leak, because that would have sucked to debug. Verified by running server and stress client over an hour but making sure...

@biggranben I have released 0.5.0 with the unwrap removed, please download and try it out! This issue highlighted another issue that I need to limit number of concurrent request on...

Yes this is what I saw as well, it no longer crashes when the GPU is overloaded due the amount of requests. But it "freezes" when the GPU memory gets...

@biggranben please try 0.6.0 and see if removes the freezes. I could overload my server with 1000 frames in a second and it was able to process them all and...

Ok, I did expect some worse performance. I think I need to implement some stats so we can get a understanding how hard your service gets hammered. I also will...