Skip to main content
Participant
February 15, 2009
Question

FMS' system requirements seem high. Why?

  • February 15, 2009
  • 1 reply
  • 462 views
My question may seem rhetorical but isn't really. I'm accustomed to the Real Media Helix server, which I've run for several years on an eight year old 733mhz x86 processor with 768mb memory on Win 2003. Don't laugh ;-), it's true and works well *for our number of typically connected users (double digits).*

So to me it makes sense to clarify what FMS is doing besides reading files and managing a network connection. Is there, for example, non-obvious CPU-bound processing going on in there?

I thank you.

    This topic has been closed for replies.

    1 reply

    February 15, 2009
    There are two versions of FMS... FMSS (streaming server) and FMIS (interactive server). FMIS has a complete scripting engine, supports remote shared objects, recording, and a wealth of other features. Helix (as I understand helix) just pushes bits.

    Incidentally... Realplayer is malware, and I really do feel it needs to be taken off the market permanantly. Read in here:

    http://blog.jaycharles.net/?p=9
    http://blog.jaycharles.net/?p=13
    http://blog.jaycharles.net/?p=17



    fburleighAuthor
    Participant
    February 15, 2009
    quote:

    Originally posted by: JayCharles
    There are two versions of FMS... FMSS (streaming server) and FMIS (interactive server). FMIS has a complete scripting engine, supports remote shared objects, recording, and a wealth of other features. Helix (as I understand helix) just pushes bits.

    Incidentally... Realplayer is malware, and I really do feel it needs to be taken off the market permanantly. Read in here:



    Thanks Jay. So by implication the FMS software needs less then those of FMIS. I'm after some real-world data points for successful adoption approaches for FMS supporting double-digit connection counts. Memory, CPU, etc. Knowing *what* FMS is doing when its basic function is to stream hour-long media would help me put it to use, perhaps replacing our older Helix infrastructure.