Shared Component - List of Values - slow to load on Oracle Cloud

Please update your forum profile with a recognisable username instead of "User_HP5NA".

It depends entirely on what the "SQL statement" is doing...

The VERY SAME SQL can have DIFFERENT performance on the SAME DATA AND DATABASE.

SQL> set timing on 
SQL> select count(*) from dba_objects; 
 
       COUNT(*) 
---------------- 
        766,205 
 
1 row selected. 
 
Elapsed: 00:00:01.52 
SQL> select count(*) from dba_objects; 
 
       COUNT(*) 
---------------- 
        766,205 
 
1 row selected.

Elapsed: 00:00:00.73

Second execution is 50% faster.

You are now talking about different databases, different servers - and blaming a difference in performance on something the APEX team did - or are unaware of.

Unacceptable.

First learn and understand HOW the architecture and technology works before starting to throw blame around.

I've been around h/w and s/w technologies for some years. When something goes wrong, there are performance issues, or stability issues and the like - my first response is that I got something wrong. Only after doing a RCA and determining I did not muck it up, I'll look for the error or bug in the product. Which is almost never the case.

Yet in your view, with seemingly no understanding of the Oracle products used, your problem is due to the product and the lack of knowledge from the product team.

Unacceptable.

It is YOUR problem. Not APEX's problem.

Here is the performance measured from a client browser perspective, looking at client-server calls. The 1st call is to the APEX flow engine - which runs the SQL and PL/SQL code for rendering that page and returns the HTML of the page via HTTP to the browser to process (load additional resources like CSS and JS files), and render:

So the APEX flow engine constructed a 1.4MB page, that includes a page item (select list) containing 16,926 items. And this was done, and HTML page returned across the network, in 3.76 seconds.

The P1_OBJECT item definition:

Provide your evidence that APEX is at fault, or the cause is due to the APEX team's ignorance.... or accept that your ignorance is the cause of your APEX performance issue.

Your expectation about a friendly community seems to be as realistic as my expectation that s/w and the APEX team not be blamed without reason or a single shred of evidence.