5
I published a very simple codeunit as ODATA V4 endpoint:
Hi Martin,
If you are still following I've made a blog post about this and tweeted the Dynamics 365 gurus.
Both Waldo and TobyNav were familiar with the issue. Did you by any chance like me authenticate via NavUserpassword instead of using a WAC (web services access key)?
For me it was the common link in all my testing and after swapping it out in my rest client the response time dropped from 1300ms to about 10ms in BC21.
Give it a try....
Performed two further tests with OnPrem images which might be better suited for local testing:
https://bcartifacts.azureedge.net/onprem/21.2.49946.49990/nl
https://bcartifacts.azureedge.net/onprem/14.0.29537.0/nl
So to summarize MarKun BC21 doesn't seem to perform better and even significantly worse than previous versions.
Please prove me wrong @anyone
| BC Version | PingPong Response Time |
| BCv14 | 10ms |
| BCv21 | 1308ms (I actually did a few calls to get the lowest number here) |
Script for replication:
Share
Report
All responses (
Answers (
Install-Module BcContainerHelper -Force
$containername = 'Nav365v21'
$Username = 'paul'
$Password = '*****************'
$SecureString = ConvertTo-SecureString -AsPlainText $Password -Force
$credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username,$SecureString
New-BcContainer -accept_eula: $true `
-containername $containername `
-auth NavUserPassword `
-credential $credential `
-doNotExportObjectsToText `
-updateHosts `
-assignPremiumPlan `
-accept_outdated:$true `
-artifactUrl "https://bcartifacts.azureedge.net/onprem/21.2.49946.49990/nl" `
-multitenant:$false `
-isolation processcodeunit 50001 "Ping"
{
trigger OnRun()
begin
end;
procedure Ping(Pong: Text): Text
begin
exit(Pong);
end;
}
Hi Martin,
That is too bad: perhaps my work today can help you and others in a better path forward:
Our partners support team indicated that the problem probably was our setup which implies the meter will start running (it's their default response ) so I did a little more testing.
Created a basic extension called PingPong which takes a string and returns a string, nothing more.
Tested the following situations, each time testing response times against our current BC14 vs a local docker build with BcContainerHelper.
The local docker build should theoretically show a better response time as it doesn't take a trip over the internet.
The test pc is a beast with i9 and 32GB of ram.
The latter API test as yzhums indicated that Microsoft recommended the API path forward but it's performance also worsened with BC20 -> BC21.
I hope anyone can verify these results and could share Microsofts view on this?
I hope I have a wrong setting or biased setup. We refactored a large part of our WMS to work with BC webservices providing a future proof path but it seems now this was a bad call. Imagine having to make consecutive API/OData calls for an order pick and waiting 20 seconds for a result with each scan?
Hi Martin,
Did you ever find a solution?
I landed here with the same observation. We've implemented a solution based on OdataV4 unbound actions for BCv14 and it's quite fast. 50ms response time for simple queries. Today we setup a test server with an upgraded database to BCv20 and everything is 1000ms+ often worse.
Fingers crossed its an easy fix and not a reimplementation
Hi, as Josh mentiond, the API is the preferred way to integrate with Business Central.
Info from Directions NA.
Hope this helps.
Thanks.
ZHU
#1
André Arnaud de Cal...
291,419
Super User 2024 Season 2
#2
Martin Dráb
230,492
Most Valuable Professional
#3
nmaenpaa
101,156
