× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have now performed performance test and here are some figures:

Windows machine:
WIN 8 Prof - Intel I3 2 cores 3.4 Ghz, 16GB ram

IBM i V7R3 (IBM PDP) - POWER8 2 cores, 3,32 Ghz, 4GB ram

zDemo01.js (reads IFS JSON file based on QIWS/QCUSTCDT and writes
JSON output through zJsonStore

WIN: 0.7ms
IBM: 0.5ms

zDemo05.pgm, RPGLE - runs native SQL and reforms result using powerEXT/YAJL
zDemo06.js, javascript - runs db2a SQL and output JSON result via
JSON.stringify
The program basically does the same.

IBM - zDemo05.pgm: 0.7ms
IBM - zDemo06.js: 17ms

All programs are run in a sequense of call's and cold starts are left out
of the
average times.

Another little thing about running in blocked mode vs. unblocked:

When I start my HTTP daemon it writes a log that previuous was done with
console.log but now writes to a log.txt file in unblocked mode.

$Util.log('\r\n')
$Util.log('powerEXT node.js HTTP Daemon Starting')
$Util.log(' root: ' + modRoot);
$Util.log(' scope: ' + scope);
$Util.log(' port: ' + port);
$Util.log(' reloadMode: ' + funcObj.reloadMode);
$Util.log(' versions:\r\n' + JSON.stringify(process.versions, null, "\t"));

The result of console.log (blocked mode) and log.txt (unblocked mode)
is that in the console the messages comes in the sequense they are
made but in log.txt is written in a random order.

This may also be the case if you write to Data Queues where queue-entries
even from the same node.js script may be received by the backend server
program in the wrong order.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.