getStats() resource usage?

27 views
Skip to first unread message

DCT Corp

unread,
Jun 24, 2016, 2:19:57 AM6/24/16
to kurento

I was wondering how heavy of a call would these getStats() be.

We've been running this every minute to get continous stats, but we notice a considerable uptake in CPU when we do this.

Is there a good guideline of how we should be using these stats and how heavy of a load this call puts on the KMS servers?

Thanks
Hank

Ivan Gracia

unread,
Jun 24, 2016, 4:26:19 AM6/24/16
to Kurento Public
Are you collecting stats for a large number of endpoints? What's the overhead?

Ivan Gracia



--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

DCT Corp

unread,
Jun 24, 2016, 4:31:08 AM6/24/16
to Kurento Public

Correct. We are collecting stats at every minute for a groupcall of maybe 12+ and we see maybe a 10% spike in cpu and exponential growth in memory which seems to never go down when we get stats for each users incoming and outgoing. So maybe 144 endpoints?


You received this message because you are subscribed to a topic in the Google Groups "kurento" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kurento/-U2tthb8EJQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kurento+u...@googlegroups.com.

Ivan Gracia

unread,
Jun 24, 2016, 4:36:30 AM6/24/16
to Kurento Public
What version of KMS are you using? Perhaps it would be interesting to have a look at this.

@Jose what do you think? Should we open a bugtracker issue to make some thorough tests on this, in case there's a leak?

Ivan Gracia


Jose Antonio Santos Cadenas

unread,
Jun 24, 2016, 4:41:19 AM6/24/16
to kur...@googlegroups.com
There is not much that we can do now to improve the performance of this call (at least now). 

If you request the stats of 144 endpoints at the same time it's normal to have a spike and it seems not to be that big, only 10%. I think it's the expected behavior, collecting stats is a expensive operation.

Nevertheless, we will try to improve the performance on the future (but for sure not short nor mid-term).

Cheers.

Ivan Gracia

unread,
Jun 24, 2016, 4:45:17 AM6/24/16
to Kurento Public
It also looks like the memory is not going back to the previous figures.

Ivan Gracia


Jose Antonio Santos Cadenas

unread,
Jun 24, 2016, 4:47:54 AM6/24/16
to Kurento Public
How big does the memory get?
Reply all
Reply to author
Forward
0 new messages