update readme.m

benchmark/package.json

@@ -4,13 +4,13 @@
 	"description": "Compare the performance and code of multiple async patterns",
 	"main": "run.js",
 	"dependencies": {
-		"async": "1.5.2",
-		"neo-async": "1.8.2",
+		"async": "*",
+		"neo-async": "*",
 		"optimist": "^0.6.1",
-		"bluebird": "2.11.0",
-		"when": "3.7.8",
-		"co": "4.6.0",
-		"cc_co":"*"
+		"bluebird": "*",
+		"when": "*",
+		"co": "*",
+		"cc_co": "*"
 	},
 	"devDependencies": {},
 	"scripts": {

readme.md

@@ -6,7 +6,7 @@
 
 [中文](https://github.com/yyrdl/zco/blob/master/readmes/readme_ch.md)
 
-Generator based control flow, no other dependence.
+Generator based control flow with good performance, no other dependence.
 
 Recommend versions of node.js  which support the destructuring assignment syntax.
 
@@ -238,7 +238,7 @@ Full code [here](https://github.com/yyrdl/zco_example/tree/master/defer)
 
 ### 5. Consecutive Error Stack
 
-As you know ,if an error occurred in an asynchronous function, it will lose call-stack which  make it difficult to debug .
+If an error occurred in an asynchronous function, we will lose callstack which  make it difficult to debug .
 
 __Solve What__： Support Consecutive Error Stack
 
@@ -298,6 +298,8 @@ We get the full clear chain of function call ,try it by yourself :)
 
 full code [here](https://github.com/yyrdl/zco_example/tree/master/consecutive_stack)
 
+In order to get best performance, you can turn off this feature globally by call `zco.__TrackCallStack(false)`,nearly 2x faster.
+
 ### 6.zco.brief
 
 zco suppose it's possible that all operations will go wrong, so the first return-value always be error,the second one is the exact result returned by yourself.Error in different place has different meaning,we can deal with them in different way.