Hi Nathan,
I'm having a hard time reconciling two claims: (a) Node actually performs less well than synchronous programming technologies, and (b) businesses that do high volumes of web transactions say Node allowed them to process more transactions more quickly while reducing the number of servers they needed. These two things are causing a lot of cognitive dissonance in me.
I strongly suspect that my inability to reconcile these claims is due to my lack of knowledge. It's me. I'm new to this. I would be curious as to how these claims reconcile with each other. Any insights would be appreciated.
Thanks,
Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com>
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Wednesday, March 21, 2018 5:17 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WEB400] Express, React, Node.JS
On Sat, Feb 24, 2018 at 1:45 PM, Turner, Kevin (ELS-CON) <
kevin@xxxxxxxxxxxxxx<mailto:kevin@xxxxxxxxxxxxxx>> wrote:
"await comes with a performance penalty" ??
What performance penalty Henrik?
I was just reviewing old discussions and came across this.
I've read that various implementations of promise-callback functionality
offer varying performance characteristics. Those comparisons are like a
factor of 1 (say 100% degradation or improvement).
The real performance concern however is when you compare async-await
functions vs. other language environments such a Python where functions
perform I/O synchronously as opposed to using an "await" to periodically
relinquish control to the Node.js event loop.
Synchronous functions in other language environments may provide something
like 25 times better performance than asynchronous functions in Node.js.
That makes sense to me. Node.js performs concurrency services within its
event loop as opposed to other architectures that rely on the underlying OS
to perform services like task swapping. Every time a Javascript function
relinquishes control to Node's event loop via the await keyword, Node will
perform its concurrency operations (through the event-loop cycle). That can
add a lot of latency that synchronous architectures don't run into.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400<
https://lists.midrange.com/mailman/listinfo/web400>
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/web400<
https://archive.midrange.com/web400>.
midrange.com
