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
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,8 @@ SocketCluster
5
5
6
6
**See bottom of page for benchmark tests.**
7
7
8
+
### Introduction
9
+
8
10
SocketCluster is a fast, highly scalable HTTP + WebSocket (engine.io) server which lets you build multi-process
9
11
realtime systems/apps that make use of all CPU cores on a machine/instance.
10
12
It removes the limitations of having to run your Node.js server as a single thread.
@@ -20,6 +22,12 @@ SocketCluster was designed to be lightweight and its realtime API is almost iden
20
22
21
23
Follow the project on Twitter: https://twitter.com/SocketCluster
22
24
25
+
### Recent changes
26
+
27
+
v0.9.42 - Major efficiency improvement - Now using UNIX sockets instead of TCP sockets for IPC. Uses named pipes on Windows.
28
+
This change affected the API. The workers and stores start options are now just integers instead of arrays of port numbers.
29
+
Also note that the balancerCount option was renamed to balancers.
30
+
23
31
### Memory leak profile
24
32
25
33
SocketCluster has been tested for memory leaks.
@@ -29,6 +37,7 @@ No memory leaks were detected when using the latest Node.js version.
29
37
Note that leaks were found when using Node.js versions below v0.10.22 - This is probably the Node.js 'Walmart' memory leak - Not a SocketCluster issue.
0 commit comments