Skip to main content
M
Mihai_Moldovanu
Participating Frequently
February 23, 2012
Question

Origin - edge limitation on VOD but not on LIVE

  • February 23, 2012
  • 2 replies
  • 1758 views

Hi ,

we have an origin server where video materials are stored and one edge where clients are conected to.

If i allow clients to connect directly to core server it can go easily to 1000 users without any problems.

If the clients connects to edge after 100 users the player will start buffering the video every few seconds.

On the other hand if i connect a FMLE to core ( same video bitrate as materials already encoded ) clients can connect to edge and there is no problem

( tested with 1000 users ) and no buffering issues appeared.

There is no IO wait problem on core, edge is configured not to use any cache.

There is no connectivity isssue between master and edge.

Both origin and edge are 4.0.3.

Anyone experienced anything similar or has any ideea why this is happening ?

    This topic has been closed for replies.

    2 replies

    S
    Striboldt
    Participant
    March 7, 2012

    We have almost the exact same issue with our Origin/Edge setup. Though we are only streaming Live TV to our customers. It seems that when more than 20 different Live streams (1200 Kbit per stream) are pulled by the Edge server, the clients connected to the Edge starts to buffer.

    S
    Adobe Employee
    SE_0208
    Adobe Employee
    February 24, 2012

    So all 1000 or 100 users play same asset or different assets. And when you try to simulate same case with live - again do all 1000 users play same stream or different streams.

    Have you tried playing around with FLVCACHE_MAXSIZE and see if that value makes any difference.

    M
    Mihai_MoldovanuAuthor
    Participating Frequently
    February 24, 2012

    Users play different assets it's many to many situation on VOD.

    I'll play around with FLVCACHE_MAXSIZE and see if there will be a change.

    A
    Anonymous
    February 25, 2012

    Can you also write the contents of your core logs here ? I am afraid application log won’t give me any useful information about the error.

    You see just a control file written if the recording does not happen successfully and stops after creating the first file (.control).

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices