Socket.IO 0.8.7 released [Node 0.6 compatibility inside]
165 views
Skip to first unread message
Guillermo Rauch
Nov 5, 2011, 4:52:35 PM11/5/11
to sock...@googlegroups.com
This release brings more stability, bug fixes, and Node 0.6 compatibility.
0.8.7 / 2011-11-05
==================
* Fixed memory leaks in closed clients.
* Fixed memory leaks in namespaces.
* Fixed websocket handling for malformed requests from proxies. [einaros]
* Node 0.6 compatibility. [einaros] [3rd-Eden]
* Adapted tests and examples.
Client
No changes
Please simply bump your `package.json` and `npm install`!
Guillermo Rauch
LearnBoost CTO
http://devthought.com
http://devthought.com
Jonathan Chetwynd
Nov 6, 2011, 5:07:52 AM11/6/11
to sock...@googlegroups.com
Please keep jargon to a minimum.
I am struggling with failure already..
why install rather than update?
what is meant by bump, and why is it needed?
cheers
Jonathan Chetwynd
no1youknowz
Nov 6, 2011, 6:30:08 AM11/6/11
to Socket.IO
package.json looks like this:
{
"name": "name of app"
, "version": "0.0.1"
, "description": "desc of app"
, "keywords": ["keywords"]
, "author": "Me"
, "dependencies": {
"express": "2.5.0",
"socket.io": "0.8.6"
}
, "main": "app"
, "engines": { "node": ">= 0.4.0" }
}
so when a bump is needed, you just change
"socket.io": "0.8.6" => "socket.io": "0.8.7"
and then do npm install . in the dir of your app and socket.io will
be upgraded.
{
"name": "name of app"
, "version": "0.0.1"
, "description": "desc of app"
, "keywords": ["keywords"]
, "author": "Me"
, "dependencies": {
"express": "2.5.0",
"socket.io": "0.8.6"
}
, "main": "app"
, "engines": { "node": ">= 0.4.0" }
}
so when a bump is needed, you just change
"socket.io": "0.8.6" => "socket.io": "0.8.7"
and then do npm install . in the dir of your app and socket.io will
be upgraded.
nan huo
Nov 7, 2011, 4:56:50 PM11/7/11
to sock...@googlegroups.com
What about npm update socket.io. What the difference between this and the 'bump' install.
nan huo
Nov 7, 2011, 4:59:53 PM11/7/11
to sock...@googlegroups.com
Sorry for the last post, I see the difference, the bump install is a way to manage your own app's dependencies.
Szymon
Nov 6, 2011, 5:39:34 AM11/6/11
to Socket.IO
Hi,
On 5 Lis, 21:52, Guillermo Rauch <rau...@gmail.com> wrote:
> * Fixed memory leaks in closed clients.
> * Fixed memory leaks in namespaces.
Maybe I did something wrong, but memory usage is higher than ever.
~240 mb in 1 hour and growing. 0.8.6 needed more than 1 day to exceed
200 mb of memory usage.
node 0.6.0 and:
ââ⏠sock...@0.8.7
â âââ polic...@0.0.4
â âââ re...@0.6.7
â ââ⏠socket.i...@0.8.7
â âââ ugli...@1.0.6
â âââ websocke...@1.0.0
â âââ xmlhttp...@1.2.2
On 5 Lis, 21:52, Guillermo Rauch <rau...@gmail.com> wrote:
> * Fixed memory leaks in closed clients.
> * Fixed memory leaks in namespaces.
~240 mb in 1 hour and growing. 0.8.6 needed more than 1 day to exceed
200 mb of memory usage.
node 0.6.0 and:
ââ⏠sock...@0.8.7
â âââ polic...@0.0.4
â âââ re...@0.6.7
â ââ⏠socket.i...@0.8.7
â âââ ugli...@1.0.6
â âââ websocke...@1.0.0
â âââ xmlhttp...@1.2.2
Guillermo Rauch
Nov 8, 2011, 8:33:49 AM11/8/11
to sock...@googlegroups.com
Leif Jackson
Nov 8, 2011, 9:15:18 AM11/8/11
to sock...@googlegroups.com
All,
With socket.io 0.8.7 , nodejs 0.4.12 and connect 1.7.2, express 2.5.0, redis client 0.6.7, hiredis 0.1.12 and redis server , Last night I was able to send over 750 million websocket messages to a connected client without leaking, node got at high as 102m but has shrunk back to 58.9 M resident, Looking good for the new 0.8.7! Way to go Guillermo and team. These were binary messages wrapped as socket.io message type from a encoded protobuf object.
Guillermo,
With the above setup and a default redis server config on a quad core mac pro workstation is 7800 m/s expected? I was really hoping for more as node was pegged on one core, and a running profile showed most of the effort in libevent (expected) and somewhere in anonymous objects, I know there is a lot of stack in my current setup but was curious as to any throughput tests you have done? My websocket client is C++ and was only using 50% of it's CPU and that was all mostly writing the message to /dev/null.
Thanks for such a cool project and all your hard work!
Leif
With socket.io 0.8.7 , nodejs 0.4.12 and connect 1.7.2, express 2.5.0, redis client 0.6.7, hiredis 0.1.12 and redis server , Last night I was able to send over 750 million websocket messages to a connected client without leaking, node got at high as 102m but has shrunk back to 58.9 M resident, Looking good for the new 0.8.7! Way to go Guillermo and team. These were binary messages wrapped as socket.io message type from a encoded protobuf object.
Guillermo,
With the above setup and a default redis server config on a quad core mac pro workstation is 7800 m/s expected? I was really hoping for more as node was pegged on one core, and a running profile showed most of the effort in libevent (expected) and somewhere in anonymous objects, I know there is a lot of stack in my current setup but was curious as to any throughput tests you have done? My websocket client is C++ and was only using 50% of it's CPU and that was all mostly writing the message to /dev/null.
Thanks for such a cool project and all your hard work!
Leif
Szymon
Nov 8, 2011, 10:40:43 AM11/8/11
to Socket.IO
Downgraded node to 0.4.12 and everything is working fine now. Memory
leaks (all of them, at last! :D) are gone. :)
On 8 Lis, 14:33, Guillermo Rauch <rau...@gmail.com> wrote:
> If you downgrade it goes down ? Are you sure it's related to socket.io ?
>
> On Sun, Nov 6, 2011 at 2:39 AM, Szymon <szy...@mwg.pl> wrote:
> > Hi,
>
> > On 5 Lis, 21:52, Guillermo Rauch <rau...@gmail.com> wrote:
> > > * Fixed memory leaks in closed clients.
> > > * Fixed memory leaks in namespaces.
>
> > Maybe I did something wrong, but memory usage is higher than ever.
> > ~240 mb in 1 hour and growing. 0.8.6 needed more than 1 day to exceed
> > 200 mb of memory usage.
>
> > node 0.6.0 and:
>
> > ââ⏠socket...@0.8.7
> > â âââ policyf...@0.0.4
> > â âââ re...@0.6.7
> > â ââ⏠socket.io-cli...@0.8.7
> > â âââ uglify...@1.0.6
> > â âââ websocket-cli...@1.0.0
> > â âââ xmlhttprequ...@1.2.2
>
> --
> Guillermo Rauch
> LearnBoost CTOhttp://devthought.com
leaks (all of them, at last! :D) are gone. :)
On 8 Lis, 14:33, Guillermo Rauch <rau...@gmail.com> wrote:
> If you downgrade it goes down ? Are you sure it's related to socket.io ?
>
> On Sun, Nov 6, 2011 at 2:39 AM, Szymon <szy...@mwg.pl> wrote:
> > Hi,
>
> > On 5 Lis, 21:52, Guillermo Rauch <rau...@gmail.com> wrote:
> > > * Fixed memory leaks in closed clients.
> > > * Fixed memory leaks in namespaces.
>
> > Maybe I did something wrong, but memory usage is higher than ever.
> > ~240 mb in 1 hour and growing. 0.8.6 needed more than 1 day to exceed
> > 200 mb of memory usage.
>
> > node 0.6.0 and:
>
> > â âââ policyf...@0.0.4
> > â âââ re...@0.6.7
> > â ââ⏠socket.io-cli...@0.8.7
> > â âââ uglify...@1.0.6
> > â âââ websocket-cli...@1.0.0
> > â âââ xmlhttprequ...@1.2.2
>
> --
> Guillermo Rauch
> LearnBoost CTOhttp://devthought.com
Ryan Dahl
Nov 8, 2011, 4:02:26 PM11/8/11
to sock...@googlegroups.com
On Tue, Nov 8, 2011 at 7:40 AM, Szymon <szy...@mwg.pl> wrote:
> Downgraded node to 0.4.12 and everything is working fine now. Memory
> leaks (all of them, at last! :D) are gone. :)
> Downgraded node to 0.4.12 and everything is working fine now. Memory
> leaks (all of them, at last! :D) are gone. :)
Can you show us how to reproduce this memory leak?
Reply all
Reply to author
Forward
0 new messages