M
marian.edu
Guest
Since the average calls we see are nothing like this and normally the actual business logic processing takes way more time than serialisation/deserialisation I don't really try to beat them at the fastest-possible round-trip category 
Besides, it sure depends on the hardware used for testing and for me 60ms the round-trip for a server running in a docker container on an entry-level server connecting over wifi seems fair enough and closer to the typical usage we see when exposing REST micro-services for web/mobile apps. This is a typical akera.io memory footprint while a light configuration of Tomcat uses something between 128-256MB... YMMV I guess. root@e4dec28e3fed:/opt/akera# akera-server -h . demo status Running for : 51 days, 2 hours Load : 0 % Free : 4 Busy : 0 Requests : 1384 Completed : 1384 API calls : 2984 Memory : 36.42 MB Heap : 17.84 MB Agents information: | PID | State | #Req | #API | Last request | | 32 | Available | 345 | 705 | 3 hours, 42 minutes | | 35 | Available | 345 | 760 | 3 hours, 42 minutes | | 38 | Available | 347 | 789 | 3 hours, 42 minutes | | 41 | Available | 347 | 730 | 3 hours, 41 minutes | If the database connection is done over the network then you're right, on top of database licenses Client Networking runtime is required. One can get faster JSON serialisation/deserialisation from OE 11+ onward, still quite a few OE10.2 installations hanging around so we have to work something out that can still support the older OE versions if we move to JSON parser available in OE11. The 'new' PAS is technically a new product, it did make sense for PSC to drop the middle man (AIA) for REST services so they decided to simply move the old appsrv inside tomcat... as for the 'multi-threaded agent' I still fail to understand what is that exactly since the 4GL runtime clearly is still single-threaded. Having one thread/process managing multiple 4GL runtimes and call the 'bundle' multi-threaded agent looks more like a marketing thing to me but hey I'm more of a technical guy and don't really understand sales Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Besides, it sure depends on the hardware used for testing and for me 60ms the round-trip for a server running in a docker container on an entry-level server connecting over wifi seems fair enough and closer to the typical usage we see when exposing REST micro-services for web/mobile apps. This is a typical akera.io memory footprint while a light configuration of Tomcat uses something between 128-256MB... YMMV I guess. root@e4dec28e3fed:/opt/akera# akera-server -h . demo status Running for : 51 days, 2 hours Load : 0 % Free : 4 Busy : 0 Requests : 1384 Completed : 1384 API calls : 2984 Memory : 36.42 MB Heap : 17.84 MB Agents information: | PID | State | #Req | #API | Last request | | 32 | Available | 345 | 705 | 3 hours, 42 minutes | | 35 | Available | 345 | 760 | 3 hours, 42 minutes | | 38 | Available | 347 | 789 | 3 hours, 42 minutes | | 41 | Available | 347 | 730 | 3 hours, 41 minutes | If the database connection is done over the network then you're right, on top of database licenses Client Networking runtime is required. One can get faster JSON serialisation/deserialisation from OE 11+ onward, still quite a few OE10.2 installations hanging around so we have to work something out that can still support the older OE versions if we move to JSON parser available in OE11. The 'new' PAS is technically a new product, it did make sense for PSC to drop the middle man (AIA) for REST services so they decided to simply move the old appsrv inside tomcat... as for the 'multi-threaded agent' I still fail to understand what is that exactly since the 4GL runtime clearly is still single-threaded. Having one thread/process managing multiple 4GL runtimes and call the 'bundle' multi-threaded agent looks more like a marketing thing to me but hey I'm more of a technical guy and don't really understand sales Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...