Performance MRP-run Local client versus Native service
 
            
                
                    jeroenb                
                
                    Member Posts: 3                
            
                        
            
                    Dear all,
When running "the MRP-run" (>Manufacturing>Planning>planning worksheet>Functions>Calculate Regenerative Plan) i see a big difference in running as local client (via Database>Open) and connection via a Native service. Local the batch runs in about 1 hour and with the native service it runs more than 5 hours.
Specs:
technical objectversion: NAV4.0 sp1
Functional platformversion: NAV5.0sp1 and also NAV2009 R2 tried
Database size: 25000000 (kB)
Database size: 17731328 (kB)
DBMS-cache: 800000 (kB)
Commitcache: Yes
I have tried several different diskconfigurations (RAID6, RAID10, SSD) but in all the situations i see the same differences.
Who can help me with this case. I prefer a litlle change in configuration in the current Native-service, because we are on the way to migrate to a new version of NAV (NAV2013).
For the time being we need this tempory solution.
Kind regards,
Jeroen Bennink
                When running "the MRP-run" (>Manufacturing>Planning>planning worksheet>Functions>Calculate Regenerative Plan) i see a big difference in running as local client (via Database>Open) and connection via a Native service. Local the batch runs in about 1 hour and with the native service it runs more than 5 hours.
Specs:
technical objectversion: NAV4.0 sp1
Functional platformversion: NAV5.0sp1 and also NAV2009 R2 tried
Database size: 25000000 (kB)
Database size: 17731328 (kB)
DBMS-cache: 800000 (kB)
Commitcache: Yes
I have tried several different diskconfigurations (RAID6, RAID10, SSD) but in all the situations i see the same differences.
Who can help me with this case. I prefer a litlle change in configuration in the current Native-service, because we are on the way to migrate to a new version of NAV (NAV2013).
For the time being we need this tempory solution.
Kind regards,
Jeroen Bennink
0                
            Comments
- 
            The problem is that there is the network that slows down.
 Give it a try to run the client directly on the server using 127.0.0.1 as the servername. This way the service connects to the service tier but avoids using the network. My experience is that it can enhance performance a lot.Regards,Alain Krikilion
 No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
- 
            Thanks Kriki, but i am not sure this would help, but give it a try.
 I have tested to open the database via the service (on instance-name) on the server self with networkcable plugged in. The same result.
 I'll try your suggestion by using the IP-number and portnumber (IP:portnumber). Let the result know.
 If you have any other suggestion, they are welcome 0 0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 323 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
