You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+51-50Lines changed: 51 additions & 50 deletions
Original file line number
Diff line number
Diff line change
@@ -493,7 +493,7 @@ Redis. The interface in `node_redis` is to return an individual `Batch` object b
493
493
The only difference between .batch and .multi is that no transaction is going to be used.
494
494
Be aware that the errors are - just like in multi statements - in the result. Otherwise both, errors and results could be returned at the same time.
495
495
496
-
If you fire many commands at once this is going to boost the execution speed significantly (see the benchmark section). Please remember that all commands are kept in memory until they are fired.
496
+
If you fire many commands at once this is going to **boost the execution speed by up to 400%**[sic!] compared to fireing the same commands in a loop without waiting for the result! See the benchmarks for further comparison. Please remember that all commands are kept in memory until they are fired.
497
497
498
498
## Monitor mode
499
499
@@ -637,55 +637,56 @@ Here are results of `multi_bench.js` which is similar to `redis-benchmark` from
Copy file name to clipboardExpand all lines: changelog.md
+17-13Lines changed: 17 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,32 @@
1
1
Changelog
2
2
=========
3
3
4
-
## v.2.2.0 - 07, 2015 - The peregrino falcon
4
+
## v.2.2.0 - 08, 2015 - The peregrino falcon
5
+
6
+
The peregrino falcon is the fasted bird on earth and this is what this release is all about: We increased performance for heavy usage by up to **400%**[sic!] and increased overall performance for any command as well. Please check the benchmarks in the [README.md](README.md) for further details.
5
7
6
8
Features
7
9
8
-
- Added disable_resubscribing option to prevent a client from resubscribing after reconnecting (@BridgeAR)
9
-
- Added rename_commands options to handle renamed commands from the redis config (@digmxl & @BridgeAR)
10
-
- Increased performance (@BridgeAR)
11
-
- exchanging built in queue with [Petka Antonov's](@petkaantonov)[double-ended queue](https://github.com/petkaantonov/deque)
10
+
- Added rename_commands options to handle renamed commands from the redis config ([@digmxl](https://github.com/digmxl) & [@BridgeAR](https://github.com/BridgeAR))
11
+
- Added disable_resubscribing option to prevent a client from resubscribing after reconnecting ([@BridgeAR](https://github.com/BridgeAR))
- exchanging built in queue with [@petkaantonov](https://github.com/petkaantonov)'s[double-ended queue](https://github.com/petkaantonov/deque)
12
14
- prevent polymorphism
13
15
- optimize statements
14
-
- Added .batch command, similar to multi but without transaction (@BridgeAR)
15
-
- Improved pipelining to minimize the [RTT](http://redis.io/topics/pipelining) further (@BridgeAR)
16
+
- Added *.batch* command, similar to .multi but without transaction ([@BridgeAR](https://github.com/BridgeAR))
17
+
- Improved pipelining to minimize the [RTT](http://redis.io/topics/pipelining) further ([@BridgeAR](https://github.com/BridgeAR))
18
+
19
+
Bugfixes
16
20
17
-
This release is mainly focusing on further speed improvements and we can proudly say that node_redis is very likely outperforming any other node redis client.
21
+
- Fix a javascript parser regression introduced in 2.0 that could result in timeouts on high load. ([@BridgeAR](https://github.com/BridgeAR))
22
+
- Fixed should_buffer boolean for .exec, .select and .auth commands not being returned ([@BridgeAR](https://github.com/BridgeAR))
18
23
19
-
If you do not rely on transactions but want to reduze the RTT you can use .batch from now on. It'll behave just the same as .multi but it does not have any transaction and therefor won't roll back any failed commands.
20
-
Both .multi and .batch are from now on going to fire the commands in bulk without doing any other operation in between.
24
+
If you do not rely on transactions but want to reduce the RTT you can use .batch from now on. It'll behave just the same as .multi but it does not have any transaction and therefor won't roll back any failed commands.<br>
25
+
Both .multi and .batch are from now on going to cache the commands and release them while calling .exec.
21
26
22
-
Bugfixes
27
+
Please consider using .batch instead of looping through a lot of commands one by one. This will significantly improve your performance.
23
28
24
-
- Fix a javascript parser regression introduced in 2.0 that could result in timeouts on high load. (@BridgeAR)
25
-
- Fixed should_buffer boolean for .exec, .select and .auth commands not being returned (@BridgeAR)
29
+
To conclude: we can proudly say that node_redis is very likely outperforming any other node redis client.
0 commit comments