Results 1 to 2 of 2

Thread: Tuning Wowza after a instance type change

  1. #1
    Join Date
    Jun 2012

    Question Tuning Wowza after a instance type change


    I noted the following at end of wowzamediaserver_startup.log file:

    13628 [main] INFO - ***** script output start *****
    13633 [main] INFO - Tuning Wowza Media Server: m1.small
    13633 [main] INFO - Java Heap Size: 1000M
    13633 [main] INFO - MediaCache: MaxPendingWriteRequestSize: 150000000
    13634 [main] INFO - MediaCache: MaxPendingReadAheadRequestSize: 75000000
    13634 [main] INFO - MediaCache: MediaCacheStore/MaxSize: 100000000000
    13649 [main] INFO - ***** script output stop *****

    But now I changed the instance type to m1.medium. What are the new parameters? I supposed that I need to change it manually due to java process still shows the -Xmx1000M parameter.


    Renato A. Ferreira

  2. #2
    Join Date
    Dec 2007



    There is nothing to do, the pre-built EC2 AMIs are pre-tuned.


Similar Threads

  1. Which EC2 instance type is best suited for large volume streaming
    By jachai in forum Performance Tuning Discussion
    Replies: 2
    Last Post: 02-11-2014, 01:58 AM
  2. Using Wowza on instance type C3-xlarge
    By Mike Edge in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 4
    Last Post: 01-28-2014, 02:22 PM
  3. Change stream type for RTPSession
    By jay_charles in forum General Forum
    Replies: 1
    Last Post: 01-16-2014, 09:54 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