[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Planning for performance across geographies use cases\n\nThis page features common use cases for planning for performance across\ngeographies by using the map view.\nPerformance Dashboard gives you visibility into the\nlatency and packet loss of the entire Google Cloud network and\nthe performance of your project's resources.\nWith the map feature of the Performance Dashboard, you can view the\nlatency details of a specific location and point to the geographic location on\nthe map.\n\nMap view is only available when **Traffic type** is set to **To the\ninternet** . Map view shows the median round-trip time (RTT)\nto internet endpoints, excluding hybrid traffic. For more information, see\n[Latency views](/network-intelligence-center/docs/performance-dashboard/concepts/overview#latency-views).\n\nScenario: Investigate latency from a city to a Google Cloud region\n------------------------------------------------------------------\n\nA typical use case of the map view is to find the latency from a city to a\nGoogle Cloud region. For example, you might want to host your application\nin a Google Cloud region and know a range of latencies that your users\nmight see when they try to access your application from different geographies.\n\nTo view the median RTT between selected geographic areas and Google Cloud\nregions, select the **View options** tab on the Performance Dashboard\npage and then select **To the internet** for the traffic type. By default, the\n**Latency (RTT)** metric is selected.\n\nYou can view the latency summary in three ways:\n\n- Table\n- Map\n- Timeline\n\nSelect the map view to see a world map that shows the median\nRTT between selected geographic areas and Google Cloud regions. For more\ninformation about how to use these views, see\n[View project-specific latency data for traffic between Google Cloud regions and internet endpoints](/network-intelligence-center/docs/performance-dashboard/how-to/view-project-specific-latency#latency-internet).\n\nIn map view, you can do the following:\n\n- To view the median latency details of a geographic location, point to the geographic location on the map.\n- To view the median latency between a Google Cloud region and geographic locations, click the Google Cloud region. The map refreshes to display the locations with traffic in the selected region.\n- To view the latency over an interval from 1 hour to 6 weeks, click **View timeline** for a selected location and then select the interval.\n- To view the latency details for a specific region, select the region, hold the pointer over a city, and then click **View timeline**. The line in the timeline indicates the latency for that traffic path. A traffic path is a route taken by the selected Google Cloud region and internet locations to reach its destination.\n- To view the latency details over a time period, click a geographic location. The location-specific details appear in a timeline view in the sidebar panel that shows the traffic from the selected location to regions that contain VM instances.\n\nRegions and endpoints are identified with the icons specified in the following\ntable.\n\nThe following example shows the latency summary for the location `Pittsburgh`,\nand the region`us-east4` and `us-east5`. The map shows that the latency between\n`us-east4` and `Pittsburgh` is 9.18 ms, and between `Pittsburgh` and\n`us-east5` is 25.76 ms.\n\nThis data can help you decide to deploy or move future workloads\nto `us-east4` because of the lower latency experienced by the end users in\n`Pittsburgh`.\n[](/static/network-intelligence-center/docs/performance-dashboard/images/gpd-lat-geo-regions.png) Latency between internet endpoints and Google Cloud regions (click to enlarge).\n\nScenario: Identify a list of nearby Google Cloud regions with the least latency from a city\n-------------------------------------------------------------------------------------------\n\nA majority of users access your application from Pittsburgh and you want to\nminimize the latency for your end users.\n\nThe following image shows a list of Google Cloud regions that are near\nto Pittsburgh and have the least latency. The list appears when you search for\nPittsburgh. This list helps you to choose the region that has the lowest latency\nand that can optimize the deployment. In this example it's `us-east4`.\nIf you want to view the latency graph for a specific duration,\nclick **View timeline**.\n[](/static/network-intelligence-center/docs/performance-dashboard/images/gpd-lat-from-city.png) Latency between a city and nearby Google Cloud regions (click to enlarge). [](/static/network-intelligence-center/docs/performance-dashboard/images/gpd-lat-graph.png) Latency details over a time period between a city and nearby Google Cloud regions (click to enlarge).\n\nTo view latency information on the Performance Dashboard page,\nclick **Project** for Google Cloud projects or **Google Cloud**\nfor non-Google Cloud projects.\n\nScenario: Investigate latency from a city to a Google Cloud region for standard versus premium tier\n---------------------------------------------------------------------------------------------------\n\nYou want to understand the latency numbers from a city to a Google Cloud\nregion for standard versus premium tier networks.\n\nIn the Performance Dashboard, you can select the following options to\ndefine your network tier.\n\n- Show data for any tier: projects use only one tier\n- Show data only for the selected tier: available only if the traffic type is selected as **To the internet** . You can select the network tier as **Standard** or **Premium** . For more information about the network service tiers, see [Network tiers](/network-tiers/docs).\n\nThe following images show the latency for the `asia-south1` region\nover Standard tier (276.02 ms) and Premium tier network (255.14 ms).\n[](/static/network-intelligence-center/docs/performance-dashboard/images/gpd-lat-standard-tier.png) Latency from a city to a Google Cloud region for Standard network tier (click to enlarge). [](/static/network-intelligence-center/docs/performance-dashboard/images/gpd-lat-premium-tier.png) Latency from a city to a Google Cloud region for Premium network tier (click to enlarge).\n\nWhat's next\n-----------\n\n- [Project performance use cases](/network-intelligence-center/docs/performance-dashboard/concepts/use-cases-project)\n- [Planning for performance use cases](/network-intelligence-center/docs/performance-dashboard/concepts/use-cases-workload-optimization)\n- [View project-specific packet loss dashboard](/network-intelligence-center/docs/performance-dashboard/how-to/view-project-specific-packet-loss)\n- [View Google Cloud packet loss dashboard](/network-intelligence-center/docs/performance-dashboard/how-to/view-google-cloud-packet-loss)\n- [Troubleshoot Performance Dashboard](/network-intelligence-center/docs/performance-dashboard/support/troubleshooting)"]]
