Ansicht
Dokumentation
10689 - DB2 - Two tier vs 3 tier
BAL Application Log Documentation ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
DB2 - Two tier vs 3 tier
Hi John,Hi John,
I can ensure that in a 2 tier landscape DB access is fast, very fast
in comparison with a 3-tier landscape.
In fact, in a 3-tier landscape, all app servers connect to the remote
database via the EDRS API, which comes with client acess / iSeries
access, see this link for more info: http://www-
1.ibm.com/servers/eserver/iseries/access/xda/ and on the central
system where the DB resides you can see the shadow processes (
QXDAEDRSQL and QXDARECVR jobs ).
I can ensure that you will have poor performance in 3-tier ( it's
practically the same that the app servers are iSeries or xSeries ).
So I design my landscape to run just dialog tasks and spool on the
app servers, and critical batch, update, etc in the central instance.
In any case you must keep in mind that there are critical issues to
consider to have a good behaviour/performance: network must be fast,
TCP/IP must be well configured, etc. Some times people have bad
performance and it's just a poor network in the middle.
Best regards,
Joan
--- In DoNotReply@consolut.eu, "ibmjw014" <jbwassocZh...> wrote:
> Hello,
>
> In our testing of IO bound programs we see the ABAPs running
> about twice as fast on a 2 tiered test system than on our 3 tiered
> production system.
> Somewhere I remember reading that on a two tiered system DB2
> unlike oracle, bypasses the database shadow processes making the
DB2
> database access extremely fast.
> I have not been able to find any documentation from either IBM or
> SAP to confirm this. Any help or comments would be gratly
appreciated.
>
> regards
> John
Durban Tours - Südafrika Safari
General Data in Customer Master PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 2323 Date: 20240520 Time: 191714 sap01-206 ( 2 ms )
