[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Heatmap patterns for document keys\n==================================\n\nThis page shows examples of patterns that you might see in a Key Visualizer\nheatmap. These patterns can help you troubleshoot specific performance\nissues.\n\nEvenly distributed usage\n------------------------\n\nIf a heatmap shows a fine-grained mix of dark and bright colors, then reads and\nwrites are evenly distributed throughout the database. This heatmap\nlikely represents an effective usage pattern for Firestore. \n\nSequential keys\n---------------\n\nA heatmap with a single bright diagonal line can indicate a database that uses\nstrictly increasing or decreasing keys. Sequential keys\nare an anti-pattern that can create hotspots.\nTo learn more about hotspots, see the\n[best practices page](/firestore/docs/best-practices#high_read_write_and_delete_rates_to_a_narrow_document_range).\n\nWhen hotspotting, you might observe corresponding elevated latencies\nwhen you compare a `Ops/s` metric with a latency metric. \n\nSudden traffic increase\n-----------------------\n\nA heatmap with a key range that suddenly changes from dark to bright indicates\na sudden spike in load. If `Ops` traffic increases faster than\nFirestore can auto-scale resources, you might see\ncorresponding elevated `latency` metrics. \n\nWhat's next\n-----------\n\n- Learn how to [get started with Key Visualizer](./keyvis-getting-started).\n- Find out how to [explore a heatmap in detail](./keyvis-exploring-heatmaps).\n- Read about the [metrics you can view in a heatmap](./key-visualizer#metrics).\n- Learn about [index key patterns](/firestore/docs/keyvis-patterns-index)"]]
