/home/techb158/ileadtechnology.com/vendor/predis/predis/examples
NameSizeModeActions
custom_cluster_distributor.php28010644editdlrm
debuggable_connection.php23520644editdlrm
dispatcher_loop.php21660644editdlrm
executing_redis_commands.php14640644editdlrm
key_prefixing.php8910644editdlrm
lua_scripting_abstraction.php17210644editdlrm
monitor_consumer.php15730644editdlrm
pipelining_commands.php10060644editdlrm
pubsub_consumer.php20330644editdlrm
redis_collections_iterators.php28120644editdlrm
replication_complex.php26170644editdlrm
replication_sentinel.php21620644editdlrm
replication_simple.php17670644editdlrm
session_handler.php18930644editdlrm
shared.php10250644editdlrm
transaction_using_cas.php15420644editdlrm
Edit: /home/techb158/ileadtechnology.com/vendor/predis/predis/examples/pipelining_commands.php (1006B)
* * For the full copyright and license information, please view the LICENSE * file that was distributed with this source code. */ require __DIR__.'/shared.php'; // When you have a whole set of consecutive commands to send to a redis server, // you can use a pipeline to dramatically improve performances. Pipelines can // greatly reduce the effects of network round-trips. $client = new Predis\Client($single_server); $responses = $client->pipeline(function ($pipe) { $pipe->flushdb(); $pipe->incrby('counter', 10); $pipe->incrby('counter', 30); $pipe->exists('counter'); $pipe->get('counter'); $pipe->mget('does_not_exist', 'counter'); }); var_export($responses); /* OUTPUT: array ( 0 => Predis\Response\Status::__set_state(array( 'payload' => 'OK', )), 1 => 10, 2 => 40, 3 => true, 4 => '40', 5 => array ( 0 => NULL, 1 => '40', ), ) */