× 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.



Isn't it perhaps time to raise the PHP time limit? Or its memory pool, or ... call team Seiden in?

Like the others I have found that IBM i in a web environment scales very well - often handling massively increased workloads with just a simple increase in memory. No sudden requirement for server farms - just the same old box.


Jon P.



On Aug 22, 2022, at 12:39 AM, Steve Richter <stephenrichter@xxxxxxxxx> wrote:

On Sun, Aug 21, 2022 at 6:22 PM Brad Stone <bvstone@xxxxxxxxx <mailto:bvstone@xxxxxxxxx>> wrote:

On Sun, Aug 21, 2022 at 11:20 AM Steve Richter <stephenrichter@xxxxxxxxx>
wrote:


Biggest difference between IBM i and a PC web server is performance. IBM
i
just does not scale well. A web page will work great when you demo it to
the user. But a single core power 8 can get bogged down by web code and
the
SQL that serves results sets to the web pages. When that happens, code
that
worked now fails with timeout messages.



Funny, I've seen exactly the opposite. Throw a DB with over 10000 records
at a PC server and watch it TANK hard.



I can't say I have production experience coding applications on a PC
server. So I do not have a solid comparison. I just know I have written a
lot of SQL intensive IBM i code the last 5 years. The applications run
well. But I see it pushing the limits of the single core power 8 hardware
that it runs on. Especially one account where the apps are single page
vue.js web apps that make heavy use of SQL procedure calls which return
results sets to the web page. These apps have acceptable response time most
of the time. When the system bogs down the apps hit the PHP 30 second
limit. Where the PHP server just gives up. Which leaves the javascript
client code hanging. And although PHP timed out, DB2 continues to run
the SQL procedure until completion. And the web user presses the F5 key to
reload the page. Which starts another instance of the now very long running
SQL procedure. Has the potential to be a real trainwreck mess.

-Steve




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.