Bear in mind that I am only in "development" mode so basically I am the only connected client. I have only just finished the code and have not deployed it anywhere where there are likely to be numerous connected clients yet. Once I have, I will assess it again. My understanding is that it will grow/shrink the threads based on demand - that is where express.js and socket.io come into play. At this stage I was more concerned with the footprint of each child process.
-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: 02 September 2015 14:19
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Question about Node.JS and XMLSERVICE
Again, thanks for the information. It doesn't sound like six (6) threads in the main JOB would support very many Web-socket connections. I seem to recall that broadcasts require persistent connections. An Apache instance at a client's site is running upwards to 4,000 threads to support HTTP connections, which timeout after something like 60 seconds of inactivity. I wonder how scalable Node might be in comparison to the Apache based server?
Is the number of Node or Sails threads configurable?
On Wed, Sep 2, 2015 at 7:02 AM, Kevin Turner < kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:
Yes that is right. The main node app is a web socket server, and the
child node processes are listeners that wait for entries to arrive on
a keyed data queue (one child per key). When they get data, they pass
it back to main process to broadcast to the subscribed clients.
One thing I did notice when I started looking at the stats was that my
main process was consuming a ridiculous amount of CPU. A major
worry......until I realise what it was. My app is actually a Sails.js app
that uses Express.js under the covers. Sails also uses something
called Grunt that watches for changes to certain files and then redeploys them.
That was totally superfluous to my requirements, so I disabled Grunt and
the CPU usage returned to next to nothing. Phew! I didn't have the time
or inclination to find out why Grunt was doing this. I suspect I
needed to reconfigure it slightly for this platform - but I couldn't be bothered.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.
___________________________________________
This email has been scanned by iomartcloud.
http://www.iomartcloud.com/
________________________________
NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.
--------------------------------------------------------------------------------
CoralTree Systems Limited
Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton
Hampshire
SO15 2EA
VAT Registration Number 834 1020 74.
midrange.com
