Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Access Log Gigabytes vs Gigabits

  1. #1

    Default Access Log Gigabytes vs Gigabits

    Hi there,

    Please confirm where I am going wrong here.

    ACCESS LOG
    When I am looking at "Server-to-client stream bytes" it says '5644 G'

    AMAZON BANDWIDTH
    When I am looking at their stats for the SAME 24 hour period, it says 685GB (Gigabytes).

    This math would be add up properly if the 5644 G actually meant Gigabits. But the Wowza manual says Gigabytes. If this were true, I would have over 5.6TB of data transfer and that is definitely not what Amazon says (their network engineer has confirmed their 'outbound traffic' amount.

    Let me know your thoughts...thanks!
    Adrian

  2. #2

    Default

    Hi Adrian,

    Thanks for the report. Where are you seeing this? sc-bytes? Which version of Wowza?

    The Wowza User Guide says, "cs-stream-bytes: Total number of bytes transferred from client to server for stream x-stream-id (accumulative)"

    The "cs" fields all accurately report bytes for me. Didn't test "sc".

  3. #3
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    sc-bytes is bytes not bits.

    Richard

  4. #4

    Default

    Thank you Randall.

    Here is my version: owza Media Server 3 Monthly Edition 3.1.2.01 build1647

    And yes, it was sc-bytes. It just does not make sense to me.

    Cheers,
    Adrian

  5. #5

    Default

    Thanks Richard but this still does not make sense then. Amazon has confirmed that the bandwidth usage is way lower than what the Wowza log is telling me.

    How can we figure this out?

    Cheers,
    Adrian

  6. #6

    Default

    Can you post a line from your logs that has the info you're asking about? When you paste here, enclose the line in [ CODE ] BB-code blocks.

  7. #7

    Default

    To verify what Amazon is reporting, you should be able to determine the bandwidth sent by one stream through various means. For example, you could send a VOD file with a known bitrate/size, or a play a live stream with a known bitrate for a specific length of time.

  8. #8

    Default

    Actually, this is what I am doing now. We are running a simple load-test of 320 concurrent users which are streaming audio at 32kbps. When the 24 hours runs up tonight, I will check again and will post it here. This test should show me a total sc-bytes of 110.6GB (Gigabytes). Correct?

    Many thanks.

  9. #9
    Join Date
    Sep 2011
    Posts
    1,933

    Default

    Hi
    Yes 110.6GB is what I got.

    Jason

  10. #10

    Default

    Thanks Jason. Actually guys I just read that the Wowza 'Load Test' tool is not really that good for measuring user streams and it's more for testing the actual CPU on the server (which was great by the way). Do you think it's because we are not running 'real' users yet for this and the load-test tool is messing with the results?

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 1
    Last Post: 09-24-2012, 03:00 PM
  2. How to understand access.log?
    By gabrielhn in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 04-23-2012, 08:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •