Experiencing slow load times on Azure Digital Twins Explorer despite various troubleshooting attempts. Need assistance.

Giel Oomen 36 Reputation points
2023-07-12T09:06:15.9366667+00:00

Hello Microsoft or others,

Description and details:

For the past few weeks we have been experiencing a degradation in performance on the Azure Digital Twins Explorer, making us have to wait several minutes for the initial data to load (models + our twins). After testing a lot of things we have a broad idea of the origin. What we tried:

  • Empty ADT instance (no models and no twins) (no issues with load times)
  • Small or large number of digital twins in a signal Azure Digital Twins instance (insignificant impact)
  • Different tenants (no impact)
  • No models uploaded vs full REC uploaded (significant impact)
  • Network request load time - no models vs full REC (insignificant impact)
  • Caching + eager loading vs no caching + eager loading (insignificant impact)

The initial load times currently take up to several minutes (I just did an actual measurement where it took 1 minute 20 which was relatively fast, often the browser shows a page not responding message). In the network tab I can see that all models from REC (~1300) where downloaded after just 3 seconds. I then took an additional 1 minute 17 to load them to UI in order to actually view or interact with them. We are experiencing this with a team of multiple people on multiple tenants.

Conclusion:

It seems that the loading after downloading the models takes a long time in the browser, given that all models were downloaded in 3 seconds but being able to interact with them takes up to several minutes. This performance degradation is only appearing the last few weeks.

Question:

Is this a known issue, and is there a way for us to improve this performance on our side?

Thanks in advance,

Giel

Azure Digital Twins
Azure Digital Twins
An Azure platform that is used to create digital representations of real-world things, places, business processes, and people.
231 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Raes, Niko 10 Reputation points
    2023-08-02T09:48:05.68+00:00

    Case 2307250050002584 on our side.
    Issues were confirmed to coincide with increased latency on internal ADT Model API.
    No root cause provided yet.

    At the moment we're no longer experiencing the issues though, but wouldn't call the issue solved if root cause isn't known.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.