Skip to content

Commit

Permalink
Merge pull request observing#2 from johntron/master
Browse files Browse the repository at this point in the history
Fixes gramatical errors in readme
  • Loading branch information
3rd-Eden committed Jun 21, 2013
2 parents 6940acf + 4e87b7d commit a488309
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@

Thor is WebSocket benchmarking/load generator. There are a lot of benchmarking
tools for HTTP servers. You've got ab, siege, wrk and more. But all these tools
only work plain ol HTTP and have no support for WebSockets and even if they did
they wouldn't be suitable as they would be testing short running HTTP requests
only work with plain ol HTTP and have no support for WebSockets - even if they did
they wouldn't be suitable, as they would be testing short running HTTP requests
instead of long running HTTP requests with a lot of messaging traffic. Thor
fixes all of this.

Expand All @@ -13,7 +13,7 @@ Thor requires Node.js to be installed on your system. If you don't have Node.js
installed you can download it from http://nodejs.org or build it from the github
source repository: http://github.com/joyent/node.

Once you have Node.js installed, you can use bundled package manager `npm` to
Once you have Node.js installed, you can use the bundled package manager `npm` to
install this module:

```
Expand All @@ -28,7 +28,7 @@ The `-g` command flag tells `npm` to install the module globally on your system.
thor [options] <urls>
```

Thor can hit multiple URL's at once, this is useful if you are testing your
Thor can hit multiple URL's at once; this is useful if you are testing your
reverse proxies, load balancers or just simply multiple applications. The url
that you supply to `thor` should be written in a WebSocket compatible format
using the `ws` or `wss` protocols:
Expand All @@ -39,9 +39,9 @@ thor --amount 5000 ws://localhost:8080 wss://localhost:8081

The snippet above will open up `5000` connections against the regular
`ws://localhost:8080` and also `5000` connections against the *secured*
`wss://localhost:8081` server. So a total of `10000` connections will be made.
`wss://localhost:8081` server, so a total of `10000` connections will be made.

One thing to keep in mind is that you probably need to bump the amount of file
One thing to keep in mind is you probably need to bump the amount of file
descriptors on your local machine if you start testing WebSockets. Set the
`ulimit -n` on machine as high as possible. If you do not know how to do this,
Google it.
Expand Down

0 comments on commit a488309

Please sign in to comment.