Skip to main content
Participating Frequently
February 17, 2009
Question

FMS 3.5 scale up

  • February 17, 2009
  • 2 replies
  • 1001 views
I would like to deploy FMS 3.5 interactive edition on a server with 4 x Quadcore processors, 64 GB of RAM and dual 10 Gbit/s network cards. Can FMS 3.5 scale to this level? What are the maximum number of cores, RAM, etc that it can run on?

Thanks,
Justin
    This topic has been closed for replies.

    2 replies

    Participating Frequently
    February 17, 2009
    I do intend running two servers in this configuration. Currently I run servers with Windows 2003, a single quad core cpu and 4GB of RAM, running 3 FMS core processes. Using the /PAE option in the boot.ini allows the OS to use memory over the 2GB limit.

    What I would like is to push as many streams on a 10 Gbit/s connection as I can. A typical stream for me is 512 kbit/s. I feel that the bottleneck is probably the CPU rather than memory for live streams. The Adobe docs say "8-way SMP" limit, but is that 8 x processors or 8 x cores?

    Has anyone run a FMS server with a 10 Gbit/s NIC? What hardware is required?
    Participant
    February 19, 2009
    i would be very interested in this also
    at the moment i'm using it on linux64, 2x quadcore with 4gb ram and dual 1 gbit/s cards but i suspect we will get over 1gbit/s limit pretty soon so i'll have to worry about scaling over that

    on another note from what i'm seeing now it also looks like the cpu will be a bigger issue then network cards even if i tried to tweak the options presented in the docs at http://help.adobe.com/en_US/FlashMediaServer/3.5_AdminGuide/WS5b3ccc516d4fbf351e63e3d119f2925e64-7ff0.html i still have a feeling that i'll have problems as soon as i go over 500-600mb/s (which should happen like in a week or so)
    So anyone with bigger implementation could give some tips on optimizing some simple vod/live stream apps? i'm searching for weeks on the web but couldn't find more then that help.adobe.com link unfortunatelly
    (sorry justin if i hijacked your thread but i thought you might hit these issues too as they are pretty related, if it bothers you i'll open a new thread)

    thx
    Participating Frequently
    February 25, 2009
    It's nice to see that everyone one is ready to push the bleeding edge. First of all Jay is correct about the _current_ max memory usage per 32bit process; and FMS has not been yet been ported to 64 bit to take advantage of all that extra ram. On the interim however you can run multiple FMSCores on that machine.

    >> Using the /PAE option in the boot.ini allows the OS to use memory over the 2GB limit.
    This could potentially be bad. The non paged memory pool is used for socket buffers, and could limit the number of connections. Make sure you test before prematurely optimizing.

    As for the # of connections over 10GB, havn't tried it yet... but its on my todo list :)

    February 17, 2009
    What operating system are you using? I'm wondering if memory limits per process will be your limiting factor (I'm certain I read about some versions of Windows 2003 having a 2GB per process memory limit... not sure about Windows 2008 or Linux).

    You can get around such limits by running multiple FMS cores, but you'd need to plan for that in your deployment architecture.

    Truth be told, even if your OS allows you to make use of all that hardware, I might consider using multiple servers. I've never tried to get a single FMS box to push that much data (the most I've ever done is about 6Gbps on a single box)... but my gut tells me you'd be better off clustering two or three less powerful machines... if only for the benefit of redundancy and failover.