Skip to main content
Known Participant
December 24, 2010
Question

Out of memory error - JS Runtime: How many users can one connect?

  • December 24, 2010
  • 1 reply
  • 1205 views

Not talking video here.  Talking interactive apps, like chat.  Ours crashes at about 500 connected users.  When I report this I'm told "make sure you're not creating too many objects serverside" or "increase the JSRuntimeSize setting in your application.xml file to the max".

Have now done both of those things but still get this out of memory error.  Let's say I optomized my app and got 100% more connection capacity.  That would be 1,000 connected users - still nowhere near enough.

Are my dreams of 6,000 or 10,000 connected users enjoying all of the fruits of the FMS interactivity pipe dreams?  Is it not meant for sessions of that size?  Where does one find documentation or advice or application assistance on this issue?

How do large social media applications connect so many people concurrently.

Thoughts appreciated.

Thanks

    This topic has been closed for replies.

    1 reply

    Participating Frequently
    December 29, 2010

    Hi Rex,

    Can you please specify what value you are using for this tag, RuntimeSize?

    <ScriptEngine>

    <!-- This specifies the max size (Kb.) the runtime can grow to before -->

    <!-- garbage collection is performed.                                 -->

    <RuntimeSize>20480</RuntimeSize>

    </ScriptEngine>

    Have you tried increasing it to 100MB or 200MB? Also make sure you are not using extensive "trace" statements.

    Known Participant
    January 3, 2011

    Yes.  I'm using the max.

    <RuntimeSize>51200</RuntimeSize>

    See:

    http://help.adobe.com/en_US/FlashMediaServer/3.5_AdminGuide/WS5b3ccc516d4fbf351e63e3d119f2926bcf-7ff0.html#WS5b3ccc516d4fbf351e63e3d119f2926bcf-7ed2

    Don't think 100MB or 200MB would be valid settings.

    January 3, 2011

    The ressponse you got is accurate. The size of the js runtime is finite, so you'll need to manage the data you're holding on the server side very carefully. Can you give us a rundown on what it is you're keeping in RAM on the server side (objects, sharedobjects, functions, etc).

    also, if your chat system uses multiple rooms, are you creating a separate application instance for each chat room, or are you lumping everything together into a single app instance?