Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV WS - Excessive Memory Usage
njhansen
Member Posts: 37
There is a fair bit written about memory leaks due to failure to release BigText or automation objects, but has anyone had experience with the NAV WS memory footprint growing out of control in other cases?
We recently reworked our web shop to use several NAV web services. The web services run on a small server that has 4GB of memory, and the WS process has been growing until it consumes all that memory then becoming unusably slow. Currently, it takes about a day to consume all available memory, but we are in an off-peak season. Adding memory is easy enough, but I don't know how much is enough and cannot find any reason for the excessive memory usage. We've reviewed the code, to ensure that all CREATEd objects also get CLEARed.
We ran some tests with a "simple" web service that just created a row with junk data in it in a small custom table, and were able to get it to grow to about 55MB before it stabilized. We tried similarly with inserting basic sales header records, and it grew out of bounds and finally crashed (after hours).
Does anyone know of things (other than missing CLEAR commands) that can be wrong with NAV code to cause the WS to grow excessively? Is there some caching happening, and if so, is there a setting to limit it?
We recently reworked our web shop to use several NAV web services. The web services run on a small server that has 4GB of memory, and the WS process has been growing until it consumes all that memory then becoming unusably slow. Currently, it takes about a day to consume all available memory, but we are in an off-peak season. Adding memory is easy enough, but I don't know how much is enough and cannot find any reason for the excessive memory usage. We've reviewed the code, to ensure that all CREATEd objects also get CLEARed.
We ran some tests with a "simple" web service that just created a row with junk data in it in a small custom table, and were able to get it to grow to about 55MB before it stabilized. We tried similarly with inserting basic sales header records, and it grew out of bounds and finally crashed (after hours).
Does anyone know of things (other than missing CLEAR commands) that can be wrong with NAV code to cause the WS to grow excessively? Is there some caching happening, and if so, is there a setting to limit it?
0