Skip to main content
C
Cineca2
Participant
November 3, 2010
Question

Free System Page Table Entries

  • November 3, 2010
  • 1 reply
  • 1419 views

I have a FMS 3.5 installed on windows 2003 server, with a NFS file system.

Both the application directory and the data directory is on the network file system.

Every two weeks the system became unstable because the Free system PTEs go under 2000.

The only strange thing i've noticed is that the Virtual size of the FMScore grows to about 1.300.000K  after few hours from the reboot of the machine and stay to this value indipendently   from the load of the server, In another FMS installed on a machine without the network file system this value is 16.800 K.

Someone has a similar strange problem?

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    November 3, 2010

    Have you increased the size of the FLvCache from the default 500M? On all of my Win2k3 systems, large volumes of memory use tend to come from VOD applications. It seems that FMS will hold data in the FLV cache indefinitely, so if you increased the size of the cache, that would explain a core consuming so much memory.

    C
    Cineca2Author
    Participant
    November 3, 2010

    thanks for the replay.

    No, the cache is still 500MB.

    The network disk is 2TB large. Can this be a problem?

    Is there a way to make FMS to free the cache?

    thank you again

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    November 14, 2010

    FMS is likely experiencing bottlenecking in handling both a remote content and application directory when under load and translating that load into memory work items that leads to your memory growth so rapidly.  While I'm not going to be able to join you in an investigation directly without a support case, I can indicate what we would recommend in that case to get to the bottom of this and you can do it yourself.

    Really you want to find the critical bottleneck.  I would start with running the same scenario with a local application folder - typically FMS does NOT expect its application folder to be remote as there tends to be little content contained therein and threads and locking are designed around quick access to that folder.

    Following that, it's worth determining the expected throughput from the remote drive servicing your content and making sure it can keep up with the requests.  If it can't you'll actually begin to buffer threads and requests FMS side and this will appear as a memory growth while they're waiting for the disk queue to respond.  Checking disk queue length can confirm this kind of problem for you.

    Good luck with the investigation and feel free to contact us at adobe if your company needs to open a support incident to work on the case.

    Asa

    awhilloc@adobe.com

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices