程序员经验分享-hwhale

linux操作redis

2023-05-16

Linux启动redis

1、为了保证原始redis.config的准确性新建myRedis目录将redis.config文件拷贝至myRedis下

[root@linux1 bin]# ps -ef|grep redis
root       1188   1150  0 16:47 pts/0    00:00:00 grep redis
[root@linux1 bin]# redis-server /myredis/redis.conf
1189:C 15 Feb 2020 16:48:12.035 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1189:C 15 Feb 2020 16:48:12.035 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1189, just started
1189:C 15 Feb 2020 16:48:12.035 # Configuration loaded
[root@linux1 bin]# ps -ef|grep redis
root       1190      1  0 16:48 ?        00:00:00 redis-server 127.0.0.1:6379     
root       1195   1150  0 16:48 pts/0    00:00:00 grep redis
[root@linux1 bin]#

2、启动redis

[root@linux1 bin]# redis-cli -p 6379
127.0.0.1:6379> ping
PONG
127.0.0.1:6379>

3、测试代码

127.0.0.1:6379> set k1 hello
OK
127.0.0.1:6379> get k1
"hello"
127.0.0.1:6379> 
[root@linux1 bin]# redis-cli -p 6379
127.0.0.1:6379> get k1
"hello"
127.0.0.1:6379>

4、关闭redis服务

127.0.0.1:6379> shutdown
not connected> ping
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> 
[root@linux1 bin]#

5、redis-benchmark作用

测试redis性能get，set，

[root@linux1 bin]# redis-server /myredis/redis.conf
1217:C 15 Feb 2020 17:03:26.581 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1217:C 15 Feb 2020 17:03:26.581 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1217, just started
1217:C 15 Feb 2020 17:03:26.581 # Configuration loaded
[root@linux1 bin]# ps -ef|grep redis
root       1218      1  0 17:03 ?        00:00:00 redis-server 127.0.0.1:6379     
root       1223   1150  0 17:04 pts/0    00:00:00 grep redis
[root@linux1 bin]# redis-benchmark
====== PING_INLINE ======
  100000 requests completed in 2.17 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

92.27% <= 1 milliseconds
99.01% <= 2 milliseconds
99.54% <= 3 milliseconds
99.79% <= 4 milliseconds
99.93% <= 5 milliseconds
99.96% <= 6 milliseconds
100.00% <= 7 milliseconds
100.00% <= 7 milliseconds
46104.20 requests per second

====== PING_BULK ======
  100000 requests completed in 2.20 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

93.09% <= 1 milliseconds
99.78% <= 2 milliseconds
99.99% <= 3 milliseconds
100.00% <= 3 milliseconds
45372.05 requests per second

====== SET ======
  100000 requests completed in 2.14 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

92.13% <= 1 milliseconds
99.56% <= 2 milliseconds
99.92% <= 3 milliseconds
99.99% <= 4 milliseconds
100.00% <= 4 milliseconds
46663.56 requests per second

====== GET ======
  100000 requests completed in 2.31 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

90.43% <= 1 milliseconds
99.40% <= 2 milliseconds
100.00% <= 3 milliseconds
100.00% <= 3 milliseconds
43215.21 requests per second

^CCR: 45283.94


[root@linux1 bin]# redis-benchmark
====== PING_INLINE ======
  100000 requests completed in 2.02 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

95.23% <= 1 milliseconds
99.90% <= 2 milliseconds
100.00% <= 2 milliseconds
49554.02 requests per second

====== PING_BULK ======
  100000 requests completed in 2.46 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

85.42% <= 1 milliseconds
98.90% <= 2 milliseconds
99.94% <= 3 milliseconds
99.99% <= 4 milliseconds
100.00% <= 4 milliseconds
40600.89 requests per second

====== SET ======
  100000 requests completed in 2.49 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

81.46% <= 1 milliseconds
97.63% <= 2 milliseconds
99.72% <= 3 milliseconds
99.91% <= 4 milliseconds
99.96% <= 5 milliseconds
99.99% <= 6 milliseconds
100.00% <= 6 milliseconds
40128.41 requests per second

====== GET ======
  100000 requests completed in 2.18 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

93.82% <= 1 milliseconds
99.78% <= 2 milliseconds
99.99% <= 3 milliseconds
100.00% <= 3 milliseconds
45871.56 requests per second

====== INCR ======
  100000 requests completed in 2.18 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

93.24% <= 1 milliseconds
99.76% <= 2 milliseconds
99.95% <= 3 milliseconds
100.00% <= 4 milliseconds
100.00% <= 4 milliseconds
45892.61 requests per second

====== LPUSH ======
  100000 requests completed in 2.10 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

91.38% <= 1 milliseconds
99.52% <= 2 milliseconds
99.91% <= 3 milliseconds
99.95% <= 4 milliseconds
99.95% <= 5 milliseconds
99.97% <= 6 milliseconds
99.99% <= 7 milliseconds
100.00% <= 7 milliseconds
47709.93 requests per second

====== RPUSH ======
  100000 requests completed in 2.18 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

90.88% <= 1 milliseconds
99.36% <= 2 milliseconds
99.84% <= 3 milliseconds
99.94% <= 4 milliseconds
99.97% <= 5 milliseconds
100.00% <= 6 milliseconds
100.00% <= 6 milliseconds
45850.53 requests per second

====== LPOP ======
  100000 requests completed in 2.22 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

91.12% <= 1 milliseconds
99.41% <= 2 milliseconds
99.93% <= 3 milliseconds
99.95% <= 107 milliseconds
99.97% <= 108 milliseconds
100.00% <= 108 milliseconds
45024.77 requests per second

====== RPOP ======
  100000 requests completed in 2.16 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

92.19% <= 1 milliseconds
99.62% <= 2 milliseconds
99.95% <= 3 milliseconds
99.99% <= 4 milliseconds
100.00% <= 4 milliseconds
46339.20 requests per second

====== SADD ======
  100000 requests completed in 2.29 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

88.54% <= 1 milliseconds
99.21% <= 2 milliseconds
99.98% <= 3 milliseconds
99.99% <= 4 milliseconds
100.00% <= 4 milliseconds
43744.53 requests per second

====== HSET ======
  100000 requests completed in 2.26 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

87.77% <= 1 milliseconds
99.28% <= 2 milliseconds
99.93% <= 3 milliseconds
99.97% <= 4 milliseconds
100.00% <= 4 milliseconds
44189.13 requests per second

====== SPOP ======
  100000 requests completed in 2.24 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

92.10% <= 1 milliseconds
99.53% <= 2 milliseconds
99.85% <= 3 milliseconds
99.90% <= 5 milliseconds
99.94% <= 6 milliseconds
99.95% <= 9 milliseconds
100.00% <= 9 milliseconds
44682.75 requests per second

====== LPUSH (needed to benchmark LRANGE) ======
  100000 requests completed in 2.21 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

86.43% <= 1 milliseconds
98.49% <= 2 milliseconds
99.88% <= 3 milliseconds
99.99% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
45289.86 requests per second

====== LRANGE_100 (first 100 elements) ======
  100000 requests completed in 4.49 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

22.15% <= 1 milliseconds
84.37% <= 2 milliseconds
98.45% <= 3 milliseconds
99.83% <= 4 milliseconds
99.95% <= 5 milliseconds
99.99% <= 6 milliseconds
100.00% <= 6 milliseconds
22271.72 requests per second

====== LRANGE_300 (first 300 elements) ======
  100000 requests completed in 10.67 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

0.01% <= 1 milliseconds
5.09% <= 2 milliseconds
77.05% <= 3 milliseconds
91.73% <= 4 milliseconds
95.92% <= 5 milliseconds
98.88% <= 6 milliseconds
99.75% <= 7 milliseconds
99.88% <= 8 milliseconds
99.93% <= 9 milliseconds
99.95% <= 10 milliseconds
99.96% <= 11 milliseconds
100.00% <= 12 milliseconds
100.00% <= 12 milliseconds
9374.71 requests per second

====== LRANGE_500 (first 450 elements) ======
  100000 requests completed in 14.24 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

0.00% <= 1 milliseconds
0.27% <= 2 milliseconds
9.36% <= 3 milliseconds
83.10% <= 4 milliseconds
93.01% <= 5 milliseconds
97.10% <= 6 milliseconds
98.76% <= 7 milliseconds
99.48% <= 8 milliseconds
99.70% <= 9 milliseconds
99.79% <= 10 milliseconds
99.84% <= 11 milliseconds
99.86% <= 12 milliseconds
99.87% <= 13 milliseconds
99.88% <= 14 milliseconds
99.88% <= 15 milliseconds
99.88% <= 16 milliseconds
99.88% <= 17 milliseconds
99.89% <= 18 milliseconds
99.90% <= 19 milliseconds
99.90% <= 20 milliseconds
99.90% <= 21 milliseconds
99.91% <= 22 milliseconds
99.91% <= 24 milliseconds
99.91% <= 25 milliseconds
99.92% <= 26 milliseconds
99.92% <= 27 milliseconds
99.92% <= 28 milliseconds
99.92% <= 52 milliseconds
99.93% <= 55 milliseconds
99.93% <= 58 milliseconds
99.93% <= 59 milliseconds
99.94% <= 60 milliseconds
99.94% <= 62 milliseconds
99.94% <= 63 milliseconds
99.95% <= 64 milliseconds
99.95% <= 65 milliseconds
99.95% <= 81 milliseconds
99.96% <= 82 milliseconds
99.98% <= 83 milliseconds
99.99% <= 85 milliseconds
99.99% <= 86 milliseconds
100.00% <= 86 milliseconds
7020.01 requests per second

^CANGE_600 (first 600 elements): 5669.44
电脑太垃圾了！

6、默认为16个数据库

[root@linux1 bin]# redis-cli -p 6379
127.0.0.1:6379> get k1
"hello"
127.0.0.1:6379> select 7
OK
127.0.0.1:6379[7]> select 17
(error) ERR DB index is out of range
127.0.0.1:6379[7]> get k1
(nil)
127.0.0.1:6379[7]>

7、严格区分大小写支持模糊查询（默认端口）

127.0.0.1:6379> desize
(error) ERR unknown command `desize`, with args beginning with: 
127.0.0.1:6379> DBSIZE
(integer) 5
127.0.0.1:6379> keys *
1) "mylist"
2) "counter:__rand_int__"
3) "myset:__rand_int__"
4) "k1"
5) "key:__rand_int__"
127.0.0.1:6379> keys k?
1) "k1"
127.0.0.1:6379>

8、删除库、删除所有库（尽量不用）

127.0.0.1:6379> FLUSHDB
OK
127.0.0.1:6379> keys *
(empty list or set)
127.0.0.1:6379> FLUSHALL
OK
127.0.0.1:6379>

9、五种基本数据类型（String字符串，hash类似java中Map(String,object),List列表底层是个链表结构，set（String类型的无序集合，HashTable来实现的，java中集合new HashSet实际new HashMap），Zset（sorted set:有序集合，每个元素都会关联一个double类型的分数，分数可以重复））

http://redisdoc.com/
具体操作类型网站！！！！
本文内容由网友自发贡献，版权归原作者所有，本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容，请联系:hwhale#tublm.com(使用前将#替换为@)

Linux

Redis

linux操作redis 的相关文章

随机推荐

  • java daytest

    1 为什么要有类的继承性 类的继承性可以减少代码冗余度 xff0c 提高代码复用性 xff0c 提高代码操作效率 2 继承的格式 xff08 语法 xff09 子类 extends 父类 3 子类继承父类后有哪些不同 子类范围大于父类 xf

  • 【rustdesk】rust入门及 windows 客户端尝试编译

    rustup 微软建议用vs code开发 官方faq 构建rustdesk 大神构建的经验 下载了64位的版本 vs code 插件 rust analyer 介绍 Better TOML 用于更好的展示 toml文件 Error Len

  • Java中创建线程主要有三种方式

    创建线程的方式及实现 Java中创建线程主要有三种方式 xff1a 一 继承Thread类创建线程类 xff08 1 xff09 定义Thread类的子类 xff0c 并重写该类的run方法 xff0c 该run方法的方法体就代表了线程要完

  • javaTest

    一 xff1a 简答题 xff08 5分 xff09 什么是java序列化 xff0c 如何实现java序列化 xff1f 答 xff1a 序列化就是一种用来处理对象流的机制 xff0c 所谓对象流也就是将对象的内容进行流化 可以对流化后的

  • MySQL使用过程中可能出现的错误

    1 mysql下载地址下载地址 xff1a https dev mysql com downloads windows installer 8 0 html 2 更改加密方式 xff1a mysql span class token ope

  • DOM介绍BOM

    DOM介绍 D xff08 文档 xff09 可以理解为整个Web加载的网页文档 xff0c O xff08 对象 xff09 可以理解为类似window对象只来的东西 xff0c 可以调用属性和方法 xff0c 这里我们说的是docume

  • JavaScript基本概念

    本章节介绍了 JavaScript xff0c 并且讨论了它的一些基本概念 你应该已经掌握哪些知识 xff1f 节 我们假设你已经掌握了以下基础技能 xff1a 对互联网和万维网 xff08 WWW xff09 有基本的认识 熟悉超文本标记

  • HTML,CSS,以及基础javaScript

    1 HTML 是一种在 Web 上使用的通用标记语言 HTML 允许你格式化文本 xff0c 添加图片 xff0c 创建链接 输入表单 框架和表格等等 xff0c 并可将之存为文本文件 xff0c 浏览器即可读取和显示 1 1HTML 的关

  • jQuery

    jQuery是一个JavaScript函数库 jQuery是一个轻量级的 34 写的少 xff0c 做的多 34 的JavaScript库 类似于一种框架 jQuery库包含以下功能 xff1a HTML 元素选取HTML 元素操作CSS

  • 欢迎使用Maven编辑器

    Maven安装与配置 一 需要准备的东西 JDK Eclipse Maven程序包 二 下载与安装 前往https maven apache org download cgi下载最新版的Maven程序 xff1a 将文件解压到D Progr

  • No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

    运行maven时报错如下 INFO Scanning for projects INFO INFO lt cn test MavenTest gt INFO Building MavenTest 0 0 1 SNAPSHOT INFO ja

  • MySQL语法糖

    1 配置MySQL需要注意哪几个问题 用户名 xff0c 密码 xff0c 端口号 xff0c 2 如何使用root账号登录MySQL net start mysql57 mysql u root p 3 创建表 查看表 查看表定义 删除表

  • 【rustdesk】配置rsproxy.cn 以 cargo add num

    配置 rsproxy cn num库里有复数 cargo add num 网络错误 PS D span class token punctuation span XTRANS span class token punctuation spa

  • collection集合层次结构

  • Eclipse启动web项目非常缓慢，崩溃

    xml文件版本问题 xff0c 需要联网效验 xff0c 重写web xml xff0c 获取新的xml覆盖原来的就行

  • SQL语句库联系

    Studentdent S Sname Sage Ssex 学生表 Course C Cname T 课程表 SC S C score 成绩表 Teacher T Tname 教师表 1 查询 001 课程比 002 课程成绩高的所有学生的

  • Linux安装redis全步骤

    第一步 xff1a 下载安装包 访问https redis io download 到官网进行下载 第二步 xff1a 安装 1 通过远程管理工具 xff0c 将压缩包拷贝到Linux服务器中 xff0c 执行解压操作 2 进入解压文件目录

  • CMD连接数据库Orcal连接数据库进行操作

    Microsoft Windows 版本 6 1 7601 版权所有 c 2009 Microsoft Corporation 保留所有权利 C Users Administrator gt sqlplus sys root 64 loca

  • Nginx（linux安装）

    Nginx engine x 是一款是由俄罗斯的程序设计师Igor Sysoev所开发高性能的 Web和 反向代理 服务器 xff0c 也是一个 IMAP POP3 SMTP 代理服务器 在高连接并发的情况下 xff0c Nginx是Apa

  • linux操作redis

    Linux启动redis 1 为了保证原始redis config的准确性新建myRedis目录将redis config文件拷贝至myRedis下 root 64 linux1 bin ps ef grep redis root 1188

热门标签