If you are not querying based on a large array or map field, you should exempt it from indexing. Large array or map fields can approach the limit of 40,000 index entries per document. Single-field exemptions for your TTL fields. Indexing on TTL fields is enabled by default and canĪffect performance at higher traffic rates. If you use TTL (time-to-live) policies, note that the TTLįield must be a timestamp. In an IoT use case with a high write rate, for example, a collection containing documents with a timestamp field might approach the 500 writes per second limit. If you don't query based on the field with sequential values, you can exempt the field If you index a field that increases or decreases sequentially betweenĭocuments in a collection, like a timestamp, then the maximum write rate to theĬollection is 500 writes per second. High write rates to a collection containing documents with sequential values You don't use for querying, you can cut storage costs by exempting the field If you have a string field that often holds long string values that Latency for applications with high read and write rates.įor most apps, you can rely on automatic indexing as well as any error message Timestamps, can lead to hotspots which impact For documents with many fields that don't require indexing, considerīe aware that indexing fields with monotonically increasing values, such as Write latency and increases storage costs for An excessive number of indexes can increase Such sequential IDs can lead to hotspots that impact latency.Īvoid the following characters in field names because they require extraĪvoid using too many indexes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |