Is 65 ms round trip latency ok?

%3CLINGO-SUB%20id%3D%22lingo-sub-1129741%22%20slang%3D%22en-US%22%3EIs%2065%20ms%20round%20trip%20latency%20ok%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1129741%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20working%20on%20my%20first%20deployment%20of%20WVD%20and%20am%20curious%20if%20latency%20is%20too%20high.%3C%2FP%3E%3CP%3EA%20tool%20I%20came%20across%20will%20show%20me%20the%20round%20trip%20latency%2C%20and%20it's%20at%2065ms.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20reading%20that%20under%20150ms%20is%20ok%2C%20but%20I'm%20not%20sure%20if%20that's%20acceptable%20in%20the%20real%20world.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20being%20run%20within%20the%20Session%20Desktop%2C%20not%20my%20local%20computer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F167308iE4A06561581E82F8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222020-01-24_22-59-56.png%22%20title%3D%222020-01-24_22-59-56.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1133796%22%20slang%3D%22en-US%22%3ERe%3A%20Is%2065%20ms%20round%20trip%20latency%20ok%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1133796%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F84477%22%20target%3D%22_blank%22%3E%40John%20Quile%3C%2FA%3E%26nbsp%3BThe%20acceptable%20latency%20will%20vary%20depending%26nbsp%3B%20on%26nbsp%3B%20your%20use%20case%20but%20in%26nbsp%3B%20general%20you%20should%20be%20fine.%20Where%26nbsp%3B%20did%26nbsp%3B%20you%20find%20the%26nbsp%3B%20150%26nbsp%3B%20ms%26nbsp%3B%20number%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1136353%22%20slang%3D%22en-US%22%3ERe%3A%20Is%2065%20ms%20round%20trip%20latency%20ok%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1136353%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F417558%22%20target%3D%22_blank%22%3E%40dhavalg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20reply.%20It%20just%20doesn't%20feel%20as%20%22snappy%22%20as%20my%20local%20computer%2C%20so%20I'm%20not%20sure%20if%20it's%20slow%20or%20naturally%20that%20way%20and%20to%20be%20expected.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20the%20150%20figure%20I%20came%20across%20was%20from%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Foverview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Foverview%3A%3C%2FA%3E%3C%2FP%3E%3CP%3EFor%20optimal%20performance%2C%20make%20sure%20your%20network%20meets%20the%20following%20requirements%3A%3C%2FP%3E%3CUL%3E%3CLI%3ERound-trip%20(RTT)%20latency%20from%20the%20client's%20network%20to%20the%20Azure%20region%20where%20host%20pools%20have%20been%20deployed%20%3CSTRONG%3Eshould%20be%20less%20than%20150%20ms.%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3ENetwork%20traffic%20may%20flow%20outside%20country%2Fregion%20borders%20when%20VMs%20that%20host%20desktops%20and%20apps%20connect%20to%20the%20management%20service.%3C%2FLI%3E%3CLI%3ETo%20optimize%20for%20network%20performance%2C%20we%20recommend%20that%20the%20session%20host's%20VMs%20are%20collocated%20in%20the%20same%20Azure%20region%20as%20the%20management%20service.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I am working on my first deployment of WVD and am curious if latency is too high.

A tool I came across will show me the round trip latency, and it's at 65ms. 

I was reading that under 150ms is ok, but I'm not sure if that's acceptable in the real world. 

This is being run within the Session Desktop, not my local computer. 

 

2020-01-24_22-59-56.png

2 Replies
Highlighted

@John Quile The acceptable latency will vary depending  on  your use case but in  general you should be fine. Where  did  you find the  150  ms  number?

Highlighted

@dhavalg 

Thanks for reply. It just doesn't feel as "snappy" as my local computer, so I'm not sure if it's slow or naturally that way and to be expected. 

 

And the 150 figure I came across was from here: https://docs.microsoft.com/en-us/azure/virtual-desktop/overview:

For optimal performance, make sure your network meets the following requirements:

  • Round-trip (RTT) latency from the client's network to the Azure region where host pools have been deployed should be less than 150 ms.
  • Network traffic may flow outside country/region borders when VMs that host desktops and apps connect to the management service.
  • To optimize for network performance, we recommend that the session host's VMs are collocated in the same Azure region as the management service.