OHS, EPG, and APEX Listener Compared - Expert Oracle Application Express

Databases Reference

In-Depth Information

it improves performance to 6.8 connections per second, with far fewer (but still some) failed

connections. This means that by changing a single parameter we went from supporting around 102

requests per minute to 408 requests, a four-fold increase. Note that these tests were performed on a very

old, very low spec test machine and are not indicative of the sorts of figures you should be trying to

achieve on your production system! As I mentioned earlier, the important thing here is the difference

between the figures, not the figures themselves.

You might be wondering how the OHS performed with the same test. I found with mod gzip and

mod expires disabled, the OHS was able to handle around 20 connections per second (with no failures).

When I enabled both mod gzip and mod expires the performance stayed the same; however, upon

investigation this was because the HTTPerf tool does not handle compressed content or handle expiry

headers correctly—unlike a real browser. In other benchmarking tests I've performed, the best the OHS

with mod gzip and mod expires correctly configured performed significantly better than an OHS server

without those two modules enabled.

Configuring EPG Parameters and DADS

You saw in the section on the OHS how we defined the DAD in the dads.conf file. So how would you

achieve the same functionality using the EPG? How could you, for example, provide different dads to

your end users? Also, how can you view and change the parameters for the EPG?

Well, most of the configuration is done using the DBMS EPG package, which contains a lot of useful

helper routines, as shown in Listing 1-11.

Listing 1-11. DBMS_EPG Package Routines

SQL> desc dbms epg;

PROCEDURE AUTHORIZE DAD