Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-2208600.1
Update Date:2017-05-17
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  2208600.1 :   Diagnosing Increase in Memory Usage on Session Border Controller after Upgrading from 6.x to 7.x  


Related Items
  • Acme Packet 4500
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
  •  




In this Document
Purpose
Details
References


Created from <SR 3-13665737451>

Applies to:

Acme Packet 4500 - Version S-Cx6.4.x and later
Information in this document applies to any platform.

Purpose

This document outlines common causes for increased memory usage on a SBC device after an upgrade, and the limitations of the SDN Service Team to predict or diagnose these changes under a standard "Break/Fix" support charter.

Details

It is expected that memory usage will increase with each feature release. So when moving from 6.4 to 7.3,many feature releases are added, all of which would have incrementally increased the memory usage. Hence a single jump from 6.4 to 7.3 is likely to have some noticeable memory usage changes.

Depending on the functionality in use and the call flows being involved, there may be more or less memory used when switching from one release to the next ( 6.x to 7.x ).  There are lots of reasons that could be a factor here:

  • New features use more memory (even if not enabled)
  • Moving from 32-bit to 64-bit (each pointer stored in the code now uses8-bytes, rather than 4-bytes)
  • Change in system memory allocator used (VxWorks/chunkAllocator to tcMalloc)
  • Change in operating system overhead (VxWorks to Linux)

Such requests from customers is beyond the scope of the Oracle Support contract. Global Customer Support cannot provide such guidance, nor can we calculate capacity levels. This is because even small configuration and/or traffic differences can have a large impact on the performance/capacity levels that can be reached. Every customer deployment enables a different set of features, has a different configuration and different call flows, which all affect memory usage in different ways.

For such concerns, Oracle Consulting should be referred to replicate the exact customer environment, such that quantitative analysis can be completed for their capacity levels on particular software versions.

References

<BUG:19760553> - [PD00058974]COMPARATIVE USAGE OF MEMORY IN SBC WITH VERSIONS 6.1.0 AND 7.1.2
<NOTE:2184017.1> - Best Common Practice for Upgrading 3820 or 4500 Session Border Controllers from 6.4.0m*p* to 7.3.0m*p*

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback