Geek asks and answers

Does using a GUID (or similar) have performance limitations in Redis?

Does using a GUID or ulong use a Redis DB key value?

Seems like: Does Redis name length decrease?

+5
source share
3 answers

Redis uses a hash strategy to store all keys, each key is stored using a hash function. All Redis db key actions fall into this function - or something related.

The original key is also stored to determine future quantities between different keys, and yes large keys can affect the memory descriptor and all related fields: memory fragmentation, hit / miss cache, etc.

+3
source

, . . Pfreixes .

GUID ( ), 300 + O (1). : Redis?.

GUID 32-36 , . , Redis , 128 (16 ). .

, : http://redis.io/topics/data-types-intro

+8

GUID:

Redis, (SQL Server, MongoDB) () , .

, Redis ?

GUID, GUID , .

http://www.developmentalmadness.com/archive/2010/10/13/sequential-guid-algorithm-ndash-improving-the-algorithm.aspx

SQL Server GUID

The longer your key, the more memory is required to store the index. GUID - 128 bits. In many (most) databases, you can also use a 64-bit or 32-bit key. Using a GUID where a 32-bit integer will be executed means that you are using 4x for indexes. Since many databases have indexes that are significantly larger than physical memory, this can have a significant impact on performance.

+1
source

More articles:


All Articles