部署大规模flash流媒体服务器_Flask流媒体服务器资源-CSDN文库

5星 · 超过95%的资源需积分: 9 16 浏览量 2011-04-11 14:37:31 上传评论收藏 917KB PDF 举报

### 部署大规模Flash流媒体服务器：关键知识点解析 #### 一、大规模部署概览与规划在当今数字化时代，视频流媒体服务已成为互联网应用的重要组成部分，而Adobe Flash Media Interactive Server (FMIS) 3.5作为业界领先的流媒体传输解决方案，在大规模部署下能够满足高需求的媒体流传输至Adobe Flash平台。大规模部署通常涉及多台服务器的联合作业，旨在提升容量和服务质量，确保媒体流的连续性与用户体验。 #### 二、容量规划与选择在进行大规模部署前，必须进行细致的容量规划。这包括评估网络带宽、存储需求、缓存策略以及安全措施等关键因素。数据中心的选择（本地或远程）是决定网络延迟和成本的关键。此外，高效的负载均衡机制对于管理大量并发连接至关重要。 #### 三、部署架构设计大型部署通常采用分布式架构，通过多个数据中心来分散负载，提高冗余度和可靠性。FMIS提供两种配置模式：Edge and Origin（边缘与源站）配置和Origin-Only Cluster（仅源站集群），每种模式都有其独特的优点和适用场景。Edge配置适合处理直播流，而Origin配置更适用于视频点播（VOD）服务。 #### 四、存储与缓存管理存储和缓存管理是大型流媒体部署中的核心问题。合理的缓存策略可以显著减少对后端服务器的请求，提高响应速度，降低延迟。同时，选择合适的存储解决方案，如固态硬盘（SSD）或网络附加存储（NAS），对保障流媒体服务质量至关重要。 #### 五、直播流与视频点播的差异处理理解直播流与视频点播（VOD）的部署差异对于优化资源分配和提高效率至关重要。直播流要求实时传输，因此需要更高的带宽和更低的延迟，而VOD则可利用缓存技术减轻服务器负担。针对不同类型的媒体内容，采用不同的负载均衡策略和数据存储方案。 #### 六、内容保护措施随着流媒体服务的普及，内容保护成为不容忽视的问题。采用加密技术和数字版权管理（DRM）系统，可以有效防止内容盗版，保护版权所有者的权益。同时，实施严格的访问控制和用户认证流程，确保只有授权用户才能访问特定内容。 #### 七、故障排查与维护在复杂的大规模部署环境中，及时有效的故障排查和系统维护至关重要。建立一套完善的监控体系，定期进行性能测试和安全性检查，可以提前发现并解决潜在问题，避免服务中断。此外，制定详尽的应急计划，确保在遇到突发状况时能够迅速恢复服务。 #### 结语部署大规模Flash流媒体服务器是一项复杂而精细的工作，涉及网络规划、硬件选型、软件配置等多个方面。通过深入理解上述关键知识点，并结合实际业务需求，可以构建出高效稳定、安全可靠的流媒体服务系统，为用户提供优质的视听体验。

资源推荐

资源详情

资源评论

TECHNICAL PAPER

Planning for Large-Scale Streaming

Deployments with Adobe Flash

Media Interactive Server 3.5

TABLE OF CONTENTS

1 Introduction to Large Scale Deployment for

Media Streaming

4 Capacity Planning and Options

6 Deployment Architecture

17 Storage and Cache

18 Live Streaming

20 Content Protection Measures

21 Troubleshooting

23 Glossary

is document covers the basic principles for deploying Flash Media Server 3.5.

Deployment options for dynamic streaming and DVR functionality will be covered in

a future version of this document.

Introduction to Large-Scale Deployment for Media Streaming

Flash Media Interactive Server (FMIS) can be deployed in large scale to meet high-

demand streaming to the Adobe Flash platform. A large-scale deployment can consist

of multiple servers linked together to increase capacity and quality of service, meaning

less interruption in the media ow and an improved user experience.

Ecient large-scale deployments should take into account issues such as datacenter

choices (local or remote), bandwidth issues, storage and cache management, authenti-

cation and security, live streaming considerations, and troubleshooting. is document

will address these issues, and will provide information needed to help make the right

choices for your network.

Large-scale deployments serve multiple users with multiple tenants, possibly with

numerous deployments across multiple data centers.

Flash Media Server oers exible solutions for large-scale deployment, with two

congurations available. Flash Media Interactive Server can be set up in a native Edge

and Origin conguration or an Origin-Only Cluster. is technical paper will discuss

the high-level benets of each.

Understanding Live vs. VOD Deployment

To ensure eciency of large-scale deployments, the type of content being delivered

must be considered. Live (“stateful”) content and video on demand (“stateless”) content

need to be handled dierently, as they each have a dierent eect on cache and disk

storage, and require a dierent level of load balancing intelligence.

Video on demand (VOD) streams can be load balanced using standard DNS or GEO load

balancing. DNS load balancing directs requests to a server closest to the location of the

consumer’s DNS server. GEO load balancing directs requests to a server closest to the

consumer’s actual IP address.

Because live streams originate from a single source, they will require more load balancing

intelligence, oen relying on server-side ActionScript to set up proxies. In this scenario,

a group of primary and backup servers will need to be dened as an ingest point for

live streams from Flash Media Live Encoder (FMLE) or third-party live encoders. is

stream would then be proxied to the Edge servers using ActionScript.

It is also good practice to leverage your stand-by capacity, allowing for your network to

scale up for large live events while using the idle capacity for VOD when not in use for

live streams.

Also, when deploying live streams, it is important that access controls be set to allow

FMLE and other encoders to publish to the server, while also setting permissions to

protect against denial-of-service (DoS) attacks and ingest overload.

Live streams will require less storage space than VOD. A possible exception to this rule

could be the use of the DVR functionality in FMS .. DVR requires that the entire live

stream be archived to allow navigation of the stream, so ample disk space will be required.

Generally, however, live streams require little or no hard drive storage.

For more details on planning large-scale

deployments, consider taking a two-day

hands-on training class. For more information,

see http://www.adobe.com/go/ndaclass

Cache handling is also dierent for live and VOD content, and is critical to network eciency,

server load, and overall quality of service. With VOD, server and network load is compounded

with the use of multi-bitrate streaming. For example, if someone is watching a stream, all of the

bit rate versions of that stream need to be cached to ensure smooth stream switching if his band-

width changes during playback. Because this would be too much to store in RAM, intelligent,

content-aware caching needs to be implemented. Also, conguring the segment cache will enable

you to manage what parts of the video are available on the Edge. For more information about set-

ting up and managing cache, refer to the Storage and Cache section of this white paper.

Protocol support

Flash Media Server communicates with connected clients using Adobe’s Real-Time Messaging

Protocol (RTMP) over Transmission Control Protocol (TCP). e RTMP connection manages

two-way communication and transmission of video, audio and data. ere are ve congura-

tions of RTMP with Flash Media Server ., as shown in the following table.

N A M E P O R T E N C R Y P T E D D E S C R I P T I O N

RTMP 1935 No Standard RTMP

HTTP 80 No (Optional) if Apache web server is installed, FMS will proxy

port 80 requests to either HTTP or RTMPT based on the

protocol.

RTMPT 80 No HTTP, with encapsulated RTMP packets

RTMPS 443 Yes Secure RTMP over SSL, requires certicate management

RTMPTS 80 Yes Secure RTMP over SSL, tunneled within HTTP

RTMPE 1935 Yes High-performance Encrypted RTMP

RTMPTE 80 Yes Encrypted RTMP tunneled within HTTP

e standard RTMP protocol will yield the best performance.

RTMPT or RTMPTE will enable you to reach more people in networks that don’t allow RTMP

or block port . However, RTMPT tunneling does reduce the capacity of Flash Media Server,

yielding 30% of RTMP (non-tunneled) trac, and requires more CPU usage.

RTMPE does require additional CPU usage as well, but still saturates a  Gbps network interface

at less than  utilization of the CPU, and is less CPU-intensive than SSL encryption.

Hardware Considerations

Flash Media Server deployments, like any large scale bandwidth-intensive hosting, benet from fast

disk access, plentiful RAM, and fast processor speeds. As seen in the following table, the listed

congurations should be sucient to saturate a  Gbps or higher network connection without

performance issues.

D E P LO Y M E N T P R O C E S S O R S R A M R A I D T Y P E

Small: one-to-many 1 Dual Core 2 - 4 GB RAID 1, 5, or 6

Medium: one-to-many or many-to-many 1 Quad Core 4 - 8 GB RAID 1, 5, or 6

Large: one-to-many or many-to-many, average shared

object usage, interactive elements

1 - 2 Quad Core 4 - 16 GB RAID 1, 10, 5, 50, or 6

Extreme: one-to-many, many-to many, extreme shared

object usage, rich interactive elements

1 - 2 Quad Core 16 - 32 GB RAID 1, 10, 5, 50, or 6

As a general rule, you’ll want to choose the fastest disks possible (, to , RPM).

RAM

An abundance of RAM is important because FMS uses it to cache content such as pre-recorded

streams, interactive content and data. A lack of RAM will force FMS to use the hard drive to

cache content, causing sluggish performance. Flash Media Server stores its cache in RAM or on

the hard drive in -kilobyte chunks, so the information is quickly accessible. Origins store

their cache in RAM, while Edges can use hard drive caching to lighten the load on the Origin.

Using the

<CacheDir> tag in Vhost.xml conguration le, Edges can be congured to cache

recorded data streams on their local hard drives, so the streams do not have to be accessed from

the Origin every time they are requested.

RTMP ports can be changed to match your

server deployment needs.

Flash Media Server stores its cache in RAM

or on the hard drive in 256-kilobyte chunks,

so the information is quickly accessible.

Origins store their cache in RAM, while Edges

can use hard drive caching to lighten the load

on the Origin.

CPU

CPU speed is also crucial to eciently handling connections, executing server-side code and

managing server operations. An overloaded CPU will cause sluggish performance, including

slower connection time and more frequent rebuering events, and may introduce latency. In gen-

eral, you can expect an  performance increase with each additional CPU/core. Two dual-core

machines will perform better than one quad-core machine. A minimum .GHz Intel® Pentium®

 CPU is recommended.

If RAM or CPU usage regularly exceed  capacity, a hardware upgrade should be seriously

considered.

When purchasing your own hardware for large FMS deployments, it is recommended that you

buy multiple copies of identical hardware congurations. is makes hardware replacement

simple in the event of hardware crashes or failures.

While Adobe does not certify specic hardware, if you require a server with an integrated hard-

ware solution, you should consider the CISCO Internet Streamer (Content Delivery Server). is

solution has precongured hardware optimized for streaming with Flash Media Server.

Network Interfaces

Since FMS . can saturate a  Gbps network interface card with as little as  CPU usage,*

you may want to consider adding multiple network cards to increase the network capacity of

your server. Using multiple network cards could increase capacity beyond 1.4 Gbps per server

(measured at 70% utilization/NIC). is is referred to as “bonding” in Linux or “teaming” in

Windows. FMS then leverages the hardware resources through the operating system, requiring

no special FMS conguration.

Issues to consider when planning network interface upgrades include:

• Your datacenter’s network connection must provide enough bandwidth to support your

server’s network capacity.

• Hard drive speed limitations could become a bottleneck. Most SATA hard drives can burst

to 3 Gbps, but can usually only sustain 1-2 Gbps of throughput. SAS hard drives with fast

rotations (10,000 RPM or higher) may help with access times and throughput. Since FMS

eciently caches data in RAM, hard disk speed may not become an issue unless there is a huge

amount of I/O activity on the disk, such as with intensive recording and viewing applications,

where hundreds of people are recording videos at the same time, and hundreds or thousands

are watching the videos.

• When using multiple NIC cards, you amalgamate the total throughput to break the 1 Gbps

limit. e sub-100% utilization of each network interface should still be observed in your

capacity planning.

• Flash Media Server can be also congured to manage multiple network cards as separate

resources. You can provision streaming at the adaptor level, binding delivery of specic media

or communications on dierent network cards. When using this solution, it is important to

remember that connections will not be persistent across the server, since data is bound to dif-

ferent network cards. is lack of persistence will aect stateful applications such as real-time

data sharing and live streaming.

• High network usage (70% of available network bandwidth) can cause extra overhead on the

CPU and memory, and bog down performance, regardless of actual network capacity.

Datacenter/Colocation Facility

You can choose to outsource your IT infrastructure or host it internally.

An in-house deployment requires hands-on management, but if qualied IT administrators are

already available, more control can be leveraged over the servers and infrastructure.

Hardware costs, maintenance, management, power, and bandwidth costs should all be considered.

In-house bandwidth and power is likely to be less expensive than external datacenters, since the

costs are not marked up by a middleman. However, an external datacenter takes care of hardware

costs and maintenance, and likely has a larger xed infrastructure and network capacity.

*Average kbps streams running on Linux

Red Hat. Refer to the ocial Adobe Flash

Media Server . white paper at http://www.

adobe.com/go/fms_whitepaper for more infor-

mation on network usage.

ere are several points to consider when considering an external datacenter or colocation facility:

• Networkreliability.Who are their bandwidth carriers and what are their reputations? Are

they Tier 1, Tier 2? Lower? Note that a carrier does not need to be Tier 1 to oer good per-

formance. Lower tier networks generally pay transit fees to other providers for data transfer,

which can result in higher fees for you, but can ultimately oer the same quality as a Tier 1.

•

Failoverandsecurity.Do their datacenters provide redundant backbone connections and

power grid connections with failover generators? Are their facilities equipped with security

systems, re suppression and eective HVAC?

•

Support.Do they keep a 24/7/365 NOC sta at all datacenters, with 24/7/365 technical sup-

port? Do all support representatives speak your native language uently? Where is the call

center located? Support sta should be located in a time zone close to yours to facilitate easy

communication during normal business hours.

•

Troubleticketresolution.What are their average response times for support tickets? Average

ticket response time should never exceed 24 hours, and would ideally be real-time.

•

Serverandnetworkmaintenance. What are the average resolution times for server, network,

power, or other failures? Reputable managed datacenter providers oer a four-hour server repair or

replacement policy in their Service Level Agreements. All facilities should have redundant net work

and power systems, but catastrophic failures should be rare and last no more than two to four

hours.

Operating System

Flash Media Server can be installed on Windows or Linux operating systems.

Microsoft® Windows Server 2008 or Windows Server® 2003 (with Service Pack 2) are supported.

Windows deployments can be easier to set up and manage than Linux, and experienced admin-

istrators can be more plentiful.

Red Hat Linux  or . deployments tend to provide more eciency, oering - better CPU

performance for live streams, and - better CPU performance for pre-recorded streams than

Windows installations.

For the most up-to-date system and operating system requirements, refer to

http://www.adobe.com/go/fms.

Capacity Planning and Options

Eectively planning a successful large-scale FMS deployment requires optimization of your

network, server hardware and FMS soware installations.

Planning for Optimal Performance

Single server deployments quickly become inadequate if you encounter signicant growth or

drastic spikes in your content volume or server trac. Peak throughput for a single server is

limited to about  Mbps, leaving a cushion for normal operating overhead. If you are con-

sistently reaching your server’s limits, the FMS logs will show frequent dropped or rejected

connections.

Geographical Distribution

Before deployment, consider your potential geographic distribution. If your user base is widely

disbursed, multiple datacenter deployments may be required to maintain a high quality of

service. If you already have a live web server, analyze your user trac statistics. If you have done

any studies or market research, incorporate those into trac projections.

Geographical location can aect latency, which results in a lower quality of service. e higher the

latency between server and client, the more limitations in throughput, which may result in a higher

instance of rebuering. Also, dierent countries have dierent limits on the public Internet, such as

rewalls, bandwidth limitations, and blocked ports.

Typical deployments can consist of anywhere from  to  regions. A region may be dened

as an area as large as the east or west coast of the United States. Some content delivery net-

works (CDNs) have global coverage, but most will tend to specialize in one area, such as North

America, Europe, or Asia-Pacic regions.

Flash Media Server can support multiple

network cards to increase the capacity of

the server. Typically 70% of total outbound

network is classed as useable bandwidth.

FOR MORE INFORMATION

For guidance with calculating your band-

width requirements, refer to the article

Calculating Bandwidth Needs for Flash

Media Server 3 at http://www.adobe.com/go/

fms_calculate_bandwidth.

剩余23页未读，继续阅读

评论收藏

内容反馈

yinbohua72

2014-06-11

感谢分享，学习到很多东西！

broodhat

粉丝: 0
资源: 2

部署大规模flash流媒体服务器

曙光液冷服务器实现大规模部署.pdf

deploy.zip docker部署流媒体服务器

wowza资料,wowza商业flash流媒体服务器

hls:快速简单地部署流媒体服务器

Web端算法部署+流媒体服务器算法部署+Flask+AI健身+Python-web实时检测效果显示

基于windows下的SRS流媒体服务器.zip

red5流媒体服务器

SlySeal 轻量流媒体服务器

nginx流媒体服务器部署所需软件

php搭建流媒体服务器 php-5.2.13.tar

graphql：:high_voltage:在无服务器基础架构上轻松，廉价地部署和管理GraphQL应用程序并大规模扩展

免部署的Windows 平台下的nginx-rtmp-win32 流媒体服务器

linux gridfs图片服务器和rmtp流媒体服务器部署完成

基于云计算的P2P流媒体服务器集群部署算法.pdf

ASP.NET-[影音娱乐]网博flash流媒体直播系统v1.0.zip

流媒体服务器Red5的扩展设计、测试与优化

流媒体技术与应用 论文

使用Flash Media Server边缘服务器

nginx流媒体服务.zip

部署文档_demo版本_v2.9.5.20200827_limit_2days.zip

Flash Media Server 3技术指南_part2.pdf

最新编译好的ZLMediaKit-windows64版本.(2024-05-30)

h.264资料pdf

播放器 FMS2

VOC.rar_ogg_voc_播放Mp3_点播 服务器

red5-rtsp视频服务器

flex-red5.zip_flex_red5_red5 flex_视频服务器

在线学习系统分布式部署方案研究.pdf

nginx-http-flv-module

red5-io-1.0.5-RELEASE

最新资源

流媒体技术与应用论文

VOC.rar_ogg_voc_播放Mp3_点播服务器