更好的性能 hget vs get || 使用 Redis

huangapple 未分类评论48阅读模式
英文:

Better Performance hget vs get || Using Redis

问题

以下是翻译好的内容:

更好的性能 hget vs get || 使用 Redis

1>
hset key field value ---这里的 field("dept") 将始终是相同的(常量),而 key 可能是20个字符

hset "user1" "dept" 1
hset "user2" "dept" 2
hset "user3" "dept" 2

2>

set key value   --这里的 key 可能是20个字符
set "{user1}dept" 1
set "{user2}dept" 2
set "{user3}dept" 3

Q1.
在这两种情况下,哪个 get cmd 将运行得更快(考虑我们的数据库有数百万个键值对)

hget "user2" "dept"  vs  get "user2" "dept"

Q2. hset "user1" "dept" 1 是否等同于 { "user1" : { "dept" : 1 }} 或者 { "dept" : { "user1" : 1 }}

Q3. 我想在 key 和 field 上实现过期,但在使用 hset 的情况下似乎不可能,有没有其他的替代方法?

英文:

Better Performance hget vs get || Using Redis

1>
hset key field value ---Here field("dept") will always be same(constant) and key could be 20 char

hset "user1" "dept" 1
hset "user2" "dept" 2
hset "user3" "dept" 2

2>

set key value   --Here key could be 20 char
set "{user1}dept" 1
set "{user2}dept" 2
set "{user3}dept" 3

Q1.
In both cases which get cmd will run faster (considering our database has millions of key value pair)

hget "user2" "dept"  vs  get "user2" "dept"

Q2. is hset "user1" "dept" 1 is equivalent to {"user1" : {"dept" : 1}} or {"dept" : {"user1" : 1}}

Q3. I want to implement expiry on key and field which is not possible in case of hset is there any alternative?

huangapple
  • 本文由 发表于 2020年4月8日 05:04:06
  • 转载请务必保留本文链接:https://java.coder-hub.com/61089387.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定