[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Features and limitations\n\nThis page provides details about vector search features and limitations.\n\nAvailability\n------------\n\nVector search is available on standalone versions from 7.2 across all tiers and all the supported regions.\n\nIndex Restrictions\n------------------\n\nThe following outlines the limitations of the index:\n\n- The maximum number of attributes in an index cannot exceed 10.\n- A vector's dimension cannot exceed 32,768.\n- The M value for HNSW must not go beyond 2M.\n- The EF Construct value for HNSW must not exceed 4096.\n- The EF Runtime value for HNSW must also not surpass 4096.\n\nScaling\n-------\n\nVector search facilitates vertical scaling through the integration of thread pools dedicated to executing vector search operations.\n\nMemory Consumption\n------------------\n\nVectors are duplicated, being stored both within the Redis keyspace and the vector search algorithm.\n\nTransactions\n------------\n\nOwing to the asynchronous nature of executing tasks by thread pools, vector search operations don't adhere to transactional semantics.\n\nRDB Snapshots\n-------------\n\n- Vector search RDB snapshots are incompatible with non-vector search Redis instances due to specialized index formatting.\n- Importing vector search RDB snapshots from other vector search solutions other than Memorystore for Redis is not supported."]]
