Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:cache_requirements [2015/04/01 09:08] – created translator1 | en:cache_requirements [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | The media server operates in connection with the installed DPI platform. [[opt_cache|It is configured by DPI platform]]. | ||
| - | To support media server, the DPI platform can be operated inline, or on the outbound traffic only, or even use PBR configuration on port 80 of the outbound traffic. | ||
| - | |||
| - | The media server is a computer with the dedicated software. It runs WEB server NGINX. It is connected into the operator' | ||
| - | |||
| - | The media server software requires CentOS 6.5. | ||
| - | |||
| - | Here are the minimal requirements for an operator with overall external bandwidth 100 Gb/s (expected cache load is up to 20% of the overall bandwidth): | ||
| - | |||
| - | - DPI platform (for outbound traffic only): SKAT-40 Complete\\ | ||
| - | - The computer: | ||
| - | < | ||
| - | 2 x Xeon E5-2650 | ||
| - | 32 GB RAM | ||
| - | 24 X 2TB HD 7200 RPM (RAID-10 | ||
| - | 2 x 10GB Ethernet to deliver the content to subscribers | ||
| - | 1 x 10Gb Ethernet for controls and content upload | ||
| - | </ | ||
| - | |||