While porting my app to use node-webkit, I've noticed a huge slowdown when
calling node APIs directly from the webkit code vs calling the node apis
through msgpack encoded RPC over websockets.
I understand one of the main goals of node-webkit is to make the
client-server interaction faster by removing the need to serialize calls,
but for some reason, it's really slow on OSX. On linux it's plenty fast as
far as I can tell with my eyes.
-------- Original Message --------
From: Tim Caswell <t...@creationix.com>
Sent: Wed Nov 07 06:29:16 格林尼治标准时间+0800 2012
To: node-webkit@googlegroups.com
Subject: [node-webkit] Slow context bridge on osx
While porting my app to use node-webkit, I've noticed a huge slowdown when
calling node APIs directly from the webkit code vs calling the node apis
through msgpack encoded RPC over websockets.
I understand one of the main goals of node-webkit is to make the
client-server interaction faster by removing the need to serialize calls,
but for some reason, it's really slow on OSX. On linux it's plenty fast as
far as I can tell with my eyes.
On Tue, Nov 6, 2012 at 4:53 PM, Roger <wen...@gmail.com> wrote:
> It should be #82, which was just fixed. After we release it today, you
> could have another try.
> ------------------------------
> *From:* Tim Caswell <t...@creationix.com>
> *Sent:* Wed Nov 07 06:29:16 格林尼治标准时间+0800 2012
> *To:* node-webkit@googlegroups.com
> *Subject:* [node-webkit] Slow context bridge on osx
> While porting my app to use node-webkit, I've noticed a huge slowdown when
> calling node APIs directly from the webkit code vs calling the node apis
> through msgpack encoded RPC over websockets.
> I understand one of the main goals of node-webkit is to make the
> client-server interaction faster by removing the need to serialize calls,
> but for some reason, it's really slow on OSX. On linux it's plenty fast as
> far as I can tell with my eyes.
-------- Original Message --------
From: Tim Caswell <t...@creationix.com>
Sent: Wed Nov 07 06:57:42 格林尼治标准时间+0800 2012
To: node-webkit@googlegroups.com
Subject: Re: [node-webkit] Slow context bridge on osx
Awesome, it's looking like this next release has everything I need!
On Tue, Nov 6, 2012 at 4:53 PM, Roger <wen...@gmail.com> wrote:
> It should be #82, which was just fixed. After we release it today, you
> could have another try.
> ------------------------------
> *From:* Tim Caswell <t...@creationix.com>
> *Sent:* Wed Nov 07 06:29:16 格林尼治标准时间+0800 2012
> *To:* node-webkit@googlegroups.com
> *Subject:* [node-webkit] Slow context bridge on osx
> While porting my app to use node-webkit, I've noticed a huge slowdown when
> calling node APIs directly from the webkit code vs calling the node apis
> through msgpack encoded RPC over websockets.
> I understand one of the main goals of node-webkit is to make the
> client-server interaction faster by removing the need to serialize calls,
> but for some reason, it's really slow on OSX. On linux it's plenty fast as
> far as I can tell with my eyes.
The fix made my OSX app much faster initially, but after I added in pty.js
(a fork(3) binding), it got super slow. Every libuv event now has around
1000ms of latency. This is using 0.3.2.
On Tue, Nov 6, 2012 at 5:47 PM, Roger <wen...@gmail.com> wrote:
> Well, the fix for node-main is to be done in 0.3.3, which will be in next
> week :-)
> ------------------------------
> *From:* Tim Caswell <t...@creationix.com>
> *Sent:* Wed Nov 07 06:57:42 格林尼治标准时间+0800 2012
> *To:* node-webkit@googlegroups.com
> *Subject:* Re: [node-webkit] Slow context bridge on osx
> Awesome, it's looking like this next release has everything I need!
> On Tue, Nov 6, 2012 at 4:53 PM, Roger <wen...@gmail.com> wrote:
>> It should be #82, which was just fixed. After we release it today, you
>> could have another try.
>> ------------------------------
>> *From:* Tim Caswell <t...@creationix.com>
>> *Sent:* Wed Nov 07 06:29:16 格林尼治标准时间+0800 2012
>> *To:* node-webkit@googlegroups.com
>> *Subject:* [node-webkit] Slow context bridge on osx
>> While porting my app to use node-webkit, I've noticed a huge slowdown
>> when calling node APIs directly from the webkit code vs calling the node
>> apis through msgpack encoded RPC over websockets.
>> I understand one of the main goals of node-webkit is to make the
>> client-server interaction faster by removing the need to serialize calls,
>> but for some reason, it's really slow on OSX. On linux it's plenty fast as
>> far as I can tell with my eyes.
Has there been any progress or updates on this? There has been a few releases since the last post and I'm curious if the problem was figured out and or resolved. Thanks.
On Wednesday, November 7, 2012 3:16:44 PM UTC-8, Tim Caswell wrote:
> The fix made my OSX app much faster initially, but after I added in pty.js > (a fork(3) binding), it got super slow. Every libuv event now has around > 1000ms of latency. This is using 0.3.2.
> On Tue, Nov 6, 2012 at 5:47 PM, Roger <wen...@gmail.com <javascript:>>wrote:
>> Well, the fix for node-main is to be done in 0.3.3, which will be in next >> week :-)
>> ------------------------------
>> *From:* Tim Caswell <t...@creationix.com <javascript:>>
>> *Sent:* Wed Nov 07 06:57:42 格林尼治标准时间+0800 2012
>> *To:* node-...@googlegroups.com <javascript:>
>> *Subject:* Re: [node-webkit] Slow context bridge on osx
>> Awesome, it's looking like this next release has everything I need!
>> On Tue, Nov 6, 2012 at 4:53 PM, Roger <wen...@gmail.com <javascript:>>wrote:
>>> It should be #82, which was just fixed. After we release it today, you >>> could have another try.
>>> ------------------------------
>>> *From:* Tim Caswell <t...@creationix.com <javascript:>>
>>> *Sent:* Wed Nov 07 06:29:16 格林尼治标准时间+0800 2012
>>> *To:* node-...@googlegroups.com <javascript:>
>>> *Subject:* [node-webkit] Slow context bridge on osx
>>> While porting my app to use node-webkit, I've noticed a huge slowdown >>> when calling node APIs directly from the webkit code vs calling the node >>> apis through msgpack encoded RPC over websockets.
>>> I understand one of the main goals of node-webkit is to make the >>> client-server interaction faster by removing the need to serialize calls, >>> but for some reason, it's really slow on OSX. On linux it's plenty fast as >>> far as I can tell with my eyes.
On Sat, Dec 8, 2012 at 4:35 PM, <matthewwr...@gmail.com> wrote:
> Has there been any progress or updates on this? There has been a few
> releases since the last post and I'm curious if the problem was figured out
> and or resolved. Thanks.
> On Wednesday, November 7, 2012 3:16:44 PM UTC-8, Tim Caswell wrote:
>> The fix made my OSX app much faster initially, but after I added in
>> pty.js (a fork(3) binding), it got super slow. Every libuv event now has
>> around 1000ms of latency. This is using 0.3.2.
>> On Tue, Nov 6, 2012 at 5:47 PM, Roger <wen...@gmail.com> wrote:
>>> Well, the fix for node-main is to be done in 0.3.3, which will be in
>>> next week :-)
>>> ------------------------------
>>> *From:* Tim Caswell <t...@creationix.com>
>>> *Sent:* Wed Nov 07 06:57:42 格林尼治标准时间+0800 2012
>>> *To:* node-...@googlegroups.com
>>> *Subject:* Re: [node-webkit] Slow context bridge on osx
>>> Awesome, it's looking like this next release has everything I need!
>>> On Tue, Nov 6, 2012 at 4:53 PM, Roger <wen...@gmail.com> wrote:
>>>> It should be #82, which was just fixed. After we release it today, you
>>>> could have another try.
>>>> ------------------------------
>>>> *From:* Tim Caswell <t...@creationix.com>
>>>> *Subject:* [node-webkit] Slow context bridge on osx
>>>> While porting my app to use node-webkit, I've noticed a huge slowdown
>>>> when calling node APIs directly from the webkit code vs calling the node
>>>> apis through msgpack encoded RPC over websockets.
>>>> I understand one of the main goals of node-webkit is to make the
>>>> client-server interaction faster by removing the need to serialize calls,
>>>> but for some reason, it's really slow on OSX. On linux it's plenty fast as
>>>> far as I can tell with my eyes.
Background: unlike Win & Linux, on Mac the renderer process of Chromium
depends on Cocoa¹ so the mainloop of Cocoa and libuv has to be
merged. And then due to possible OSX bug of handling kqueue², which
libuv is based on OSX, we made some workaround for this.
> On Sat, Dec 8, 2012 at 4:35 PM, <matthewwr...@gmail.com> wrote:
>> Has there been any progress or updates on this? There has been a few
>> releases since the last post and I'm curious if the problem was figured out
>> and or resolved. Thanks.
>> On Wednesday, November 7, 2012 3:16:44 PM UTC-8, Tim Caswell wrote:
>>> The fix made my OSX app much faster initially, but after I added in
>>> pty.js (a fork(3) binding), it got super slow. Every libuv event now has
>>> around 1000ms of latency. This is using 0.3.2.
