redis的基础使用

首先需要加载php扩展配置

window需要先查看phpinfo配置文件

http://www.libaocai.com/3436.html redis windos安装教程

查看

是nts 还是ts

http://windows.php.net/downloads/pecl/snaps/redis/2.2.5/ redis到这下载对应版本

这里也可以下载对应的dll

http://pecl.php.net/package/redis/

php加载redis扩展

extension=php_redis.dll

查看phpinfo配置是否加载了redis

需要有redis-server.exe 文件, 网上可以下载

启动服务 redis-server redis.conf

更多详情:http://blog.csdn.net/renfufei/article/details/38474435 redis使用说明

启动服务需要有这个文件redis.conf

网上也有资料

# Redis configuration file example

# By default Redis does not run as a daemon. Use ‘yes‘ if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize no

# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
# You can specify a custom pid file location here.
pidfile /var/run/redis.pid

# Accept connections on the specified port, default is 6379
port 6379

# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for connections.
#
# bind 127.0.0.1

# Close the connection after a client is idle for N seconds (0 to disable)
timeout 300

# Set server verbosity to ‘debug‘
# it can be one of:
# debug (a lot of information, useful for development/testing)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel debug

# Specify the log file name. Also ‘stdout‘ can be used to force
# the demon to log on the standard output. Note that if you use standard
# output for logging but daemonize, logs will be sent to /dev/null
logfile stdout

# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and ‘databases‘-1
databases 16

################################ SNAPSHOTTING #################################
#
# Save the DB on disk:
#
# save <seconds> <changes>
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
save 900 1
save 300 10
save 60 10000

# Compress string objects using LZF when dump .rdb databases?
# For default that‘s set to ‘yes‘ as it‘s almost always a win.
# If you want to save some CPU in the saving child set it to ‘no‘ but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes

# The filename where to dump the DB
dbfilename dump.rdb

# For default save/load DB in/from the working directory
# Note that you must specify a directory not a file name.
dir ./

################################# REPLICATION #################################

# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# slaveof <masterip> <masterport>

# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth <master-password>

################################## SECURITY ###################################

# Require clients to issue AUTH <PASSWORD> before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# requirepass foobared

################################### LIMITS ####################################

# Set the max number of connected clients at the same time. By default there
# is no limit, and it‘s up to the number of file descriptors the Redis process
# is able to open. The special value ‘0‘ means no limts.
# Once the limit is reached Redis will close all the new connections sending
# an error ‘max number of clients reached‘.
#
# maxclients 128

# Don‘t use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# ‘state‘ server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you‘ll have the time
# to upgrade. With maxmemory after the limit is reached you‘ll start to get
# errors for write operations, and this may even lead to DB inconsistency.
#
# maxmemory <bytes>

############################## APPEND ONLY MODE ###############################

# By default Redis asynchronously dumps the dataset on disk. If you can live
# with the idea that the latest records will be lost if something like a crash
# happens this is the preferred way to run Redis. If instead you care a lot
# about your data and don‘t want to that a single record can get lost you should
# enable the append only mode: when this mode is enabled Redis will append
# every write operation received in the file appendonly.log. This file will
# be read on startup in order to rebuild the full dataset in memory.
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
#
# The name of the append only file is "appendonly.log"
#
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.

appendonly no

# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don‘t fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only if one second passed since the last fsync. Compromise.
#
# The default is "always" that‘s the safer of the options. It‘s up to you to
# understand if you can relax this to "everysec" that will fsync every second
# or to "no" that will let the operating system flush the output buffer when
# it want, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that‘s snapshotting).

appendfsync always
# appendfsync everysec
# appendfsync no

############################### ADVANCED CONFIG ###############################

# Glue small output buffers together in order to send small replies in a
# single TCP packet. Uses a bit more CPU but most of the times it is a win
# in terms of number of queries per second. Use ‘yes‘ if unsure.
#glueoutputbuf yes

# Use object sharing. Can save a lot of memory if you have many common
# string in your dataset, but performs lookups against the shared objects
# pool so it uses more CPU and can be a bit slower. Usually it‘s a good
# idea.
#
# When object sharing is enabled (shareobjects yes) you can use
# shareobjectspoolsize to control the size of the pool used in order to try
# object sharing. A bigger pool size will lead to better sharing capabilities.
# In general you want this value to be at least the double of the number of
# very common strings you have in your dataset.
#
# WARNING: object sharing is experimental, don‘t enable this feature
# in production before of Redis 1.0-stable. Still please try this feature in
# your development environment so that we can test it better.
# shareobjects no
# shareobjectspoolsize 1024

以下是代码基础操作,很简单, 操作数组的时候可以使用序列化和反序列即可

<?php
ini_set(‘default_socket_timeout‘, -1);
set_time_limit(0);
$redis = new Redis();
$redis->connect(‘127.0.0.1‘, 6379);

$res=  $redis->set("test123","haha");

$arr=array("haha"=>"nihao");
$res=  $redis->set("test11",$arr);
// var_dump($res);exit;
//
//
//
$redis->del(‘tutorial-list‘);

$arr=array(
"id"=>"1",
"name"=>"zhangsan",
"age"=>"20",
);

$arr=serialize($arr);
$redis->lpush("tutorial-list", $arr);
// $redis->lpush("tutorial-list", "Redis");
//   $redis->lpush("tutorial-list", "Mongodb");
//   $redis->lpush("tutorial-list", "Mysql");
// 获取存储的数据并输出
$arList = $redis->lrange("tutorial-list", 0 ,5);
echo "返回结果:";
$a=  print_r($arList);

$a1=$redis->set("a1", $arr);
$a2=$redis->get("a1");
var_dump(unserialize($a2));
?>
时间: 2024-08-30 12:57:27

redis的基础使用的相关文章

redis使用基础(九) ——Redis虚拟内存

redis使用基础(九) --Redis虚拟内存 (转载请附上本文链接--linhxx) 一.概述 Redis的数据是保存在内存中,当物理内存不足,其会保存在虚拟内存(VM)中.Redis的vm类似操作系统的vm,其会把所有的键都存在内存中,而把部分很少被访问到的值放在硬盘中. 操作系统的vm是基于页的概念,linux每个页4KB,而redis很多对象远小于4KB.另外,redis将交换到磁盘的对象压缩,保存到磁盘的对象可以去除指针和对象元数据,这样可以减少很多的I/O操作. redis的虚拟内

redis使用基础(六) ——Redis集群

redis使用基础(六) --Redis集群 (转载请附上本文链接--linhxx) 一.单台服务器 单台redis服务器,会出现单点故障,且需要承受所有的负载.另外,所有的内容都存在单个服务器上,该服务器会成为瓶颈. 使用多台服务器作为redis服务器,需要考虑集群管理,如数据一致性.增加节点.故障恢复等问题.redis对处理这些问题有一套方案. 二.复制 redis的持久化功能保证了数据的持久性,但是如果服务器故障,数据还是可能会丢失,因此需要将数据备份到其他服务器.当一台服务器内容更新,会

redis使用基础(十) ——Redis存储Session

redis使用基础(十) --Redis存储Session (转载请附上本文链接--linhxx) 一.概述 PHP默认是将session存于服务器的文件中.当并发量大,此方式效率低,因此可以采用redis存储session. 要改变session的存储位置,首先要改变php.ini中的配置项session.save_handler,将其值设置为user. 二.改变存储位置函数 php内置的函数session_set_save_handler可以重新设定session的保存方式,包括sessio

redis使用基础(二) ——Redis数据类型

redis使用基础(二) --Redis数据类型 (转载请附上本文链接--linhxx)  一.概述 Redis是一种Key-Value类型的数据库,属于非关系型数据库,NoSQL的一种.Redis共有5种数据类型:字符串(string).散列(hash).列表(list).集合(set).有序集合(zset). 1.通配符 Redis支持部分通配符,包括?.*.[].\x,和正则表达式一致,?表示匹配0或1个,*匹配任意个,[]匹配框内的任意一个内容,\x转义,例如\?表示匹配?. 2.获取键

redis使用基础(四) ——Redis排序与消息通知

redis使用基础(四) --Redis排序与消息通知 (转载请附上本文链接--linhxx) 一.排序 1.命令 SORT key [ALPHA] [DESC] [LIMIT start end],对列表.集合和有序集合进行排序,当加上alpha参数后,则可以按照字典顺序排序,加上desc则倒序排序,加上limit则支持分页. 2.关键参数 by参数:by key:*->val,可以指定排序的标准,可以自己传入一个list,也可以指定某个列进行排序. get参数:get key:*->val

redis使用基础(一) ——Redis基本概述与安装配置

redis使用基础(一) --Redis基本概述与安装配置 (转载请附上本文链接--linhxx) 一.特性 1.存储方式 Redis采用Key-Value类型进行存储,数据存储在内存中,不存在硬盘中,由于避开了I/O,因此读写速度比关系型数据库快很多,普通的笔记本每秒可以读写超过10万个键值. 2.持久性 为了避免存在内存中导致的程序退出后数据丢失问题,Redis提供将数据异步写入硬盘,不影响继续提供服务. 3.灵活性 Redis可以为每个键设置生存时间,到期后自动删除.就此而言可以将其用作缓

redis使用基础(五) ——Redis数据持久化

redis使用基础(五) --Redis数据持久化 (转载请附上本文链接--linhxx) 当服务器突然发生问题,或者redis重启,如果希望将数据持久化在硬盘中,下次开启redis还有数据时,redis提供了两种方案,一个叫做RDB(通过内存快照(Snapshotting)实现),另一个叫做AOF(日志追加(Append-only file)).通常结合两种方式来实现redis的持久化. 1.RDB RDB通过内存快照实现,会将redis当前的全部数据以快照的方式写入二进制文件中.实现快照有以

redis使用基础(七) ——Redis管理

redis使用基础(七) --Redis管理 (转载请附上本文链接--linhxx) 一.安全性 1.运行环境 Redis以简洁为美,其安全性没有太多操作,要求在生产系统中外界不能直接连接Redis进行操作,而必须经过程序中转后,由程序进行操作. 即,redis要求运行在可信的环境中. redis服务器启动后,默认允许外界连接,可以修改其配置文件的bind,配置只能有一个路径进行连接,如bind 127.0.0.1,只允许本机连接.bind只能配置一个ip,因此设置应在防火墙中进行. 2.密码

redis使用基础(十一) ——Redis特殊情况处理机制

redis使用基础(十一) --Redis特殊情况处理机制 (转载请附上本文链接--linhxx) 一.内存淘汰 当redis的内存不足时,需要采取内存淘汰的方法,共有两种方法.一是启用虚拟内存的方式,即将redis配置文件中的vm-enabled设置成yes:二是启用内存淘汰机制,即将redis配置文件中的maxmemory设置成一个大于0的整数. redis内存淘汰机制共有三种:随机淘汰(随机挑选键进行淘汰).LRU淘汰(查找键中最近最少访问的进行淘汰).TTL淘汰(查找键中离过期时间最近的

Redis数据库基础操作

MySQL和Redis的区别 """ redis: 内存数据库(读写快,IO操作少).非关系型(操作数据方便) mysql: 硬盘数据库(数据持久化,IO操作多).关系型(操作数据间关系) 大量访问的临时数据,才有redis数据库更优 """ redis和memcache的区别 """ redis: 操作字符串.列表.字典.无序集合.有序集合 | 支持数据持久化(数据丢失可以找回.可以将数据同步给mysql) | 高