We've been looking into squeezing some more posting speed on a site that is getting close to go-live. Posting speed is important to them, as often a customer will be standing there waiting. With the usual index, SIFT, and minor code tweaks we've gained about a 20% reduction in posting time. Using a 100 line example sales order, we are seeing about an 18 second posting time in the WMS (Directed Ship) location. That is for ship and invoice. In the non-WMS location, we see about 9 seconds for a same size document. I attribute this difference to not having to also post the Warehouse Shipment.
I consider these to be fairly decent times. But I'm just looking to see if anyone has any thoughts on where more could be gained. Short of redesigning the whole posting routine. Also is this inline with the posting performance you have seen?
Not looking for a pre-defined solution. More thoughts and ideas.
There are no bugs - only undocumented features.
0
Comments
Check out http://blogs.msdn.com/b/nav/archive/2012/08/31/background-posting-and-job-queue-in-microsoft-dynamics-nav-2013.aspx
Tino Ruijs
Microsoft Dynamics NAV specialist
Background posting is a great feature and useful in many situations. This just isn't one of them. All background posting would do is re-locate the "problem". The process would not be any faster. In fact it might actually be slower in some situations. While background posting does "free up" the user to do something else, they are still waiting on the results and documents from the posting. It also has the same blocking impact on other users. Which is another reason for looking to reduce the posting time.
Anyways, thanks for the response. You raised something we had looked into but felt it just don't fit here.
And you checked the fields on inventory setup "Automatic Cost Posting", "Automatic Cost Adjustment" and "Expected Cost Posting to G/L"?
Tino Ruijs
Microsoft Dynamics NAV specialist
"Automatic Cost Posting" is ON.
"Automatic Cost Adjustment" is OFF
"Expected Cost Posting to G/L" is ON.
While I'm aware of the performance gains from turning those off, that is at a cost of functionality. Turning these off is not an option, and knowing the customer's business process I would agree with them.
It's actually been helpful to find you are thinking of the same things I have. But if you come across something I may not have thought of, feel free to send it along. I'm not looking to trade functionality for performance. But rather gain performance where I can. If I can. It may be that this is the best to be reasonably expected. Just that people are asking.
https://customers.microsoft.com/Pages/CustomerStory.aspx?recid=16608
Adaptive Business Solutions
http://justjewelrysoftware.com