# Wowza Live Streaming Sizing

**URL:** <https://community.wowza.com/t/wowza-live-streaming-sizing/47026>\
**Category:** Wowza Streaming Engine\
**Created:** [May 9, 2016, 8:07am UTC](https://community.wowza.com/t/wowza-live-streaming-sizing/47026 "2016-05-09T08:07:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Jason\_Hatchett](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hatchett/32/391_2.png) [@Jason\_Hatchett](https://community.wowza.com/u/Jason_Hatchett)\
**Post date:** [May 16, 2016, 3:08am UTC](https://community.wowza.com/t/wowza-live-streaming-sizing/47026/2 "2016-05-16T03:08:00Z")

</div>

Hello Nuno,

I will refer to your other post and the response I provided there first in regards to using a single Wowza instance:

> [@Wowza Media server Sizing for 3000 attendees](http://community.wowza.com/t/-/47025):
>
> Hello, I’am trying to size a video broadcast solution for 3000 attendees. The idea is to integrate Wowza with Cisco TCS. The operation would be as follows: 1x Video Endpoint -\> Cisto TCS -\> Wowza The issue I’m having is with sizing number of instances and the physical server to support this solution. Cisco TCS will allow a maximum of 2 simultaneous independent streams. This is the sizing I’m considering for 3000 attendees: 6 instances of Wowza media server Based on the performance Ben…

However for the scenario you are proposing here it sounds like you want to set-up Scaling using Wowza HTTP Origin applications to allow caching on a HTTP Proxies as described here:

> **[Scale with Wowza HTTP Origin applications](https://www.wowza.com/docs/scaling-with-wowza-http-origin-applications)**
>
> Understand HTTP Origin applications in Wowza Streaming Engine.

Please let me know if I can clarify any of this for you, or if you still have questions that I can assist with.

Regards

Jason Hatchett

---

_[View the full topic](https://community.wowza.com/t/wowza-live-streaming-sizing/47026)._