|
Understanding Oracle Architecture
Why It is important? It is told by an example and i will summarize this example
There is an SQl server code and it is wanted to be compiled and executed on Oracle
In this case SQL server architecture and How you use SQL server impacted the Oracle
implementation.Two wrong decision was taken..
- Keep connection Architecture same
- Use literal(non-bound) SQL
Use A Single Connection in Oracle
In SQL server if you have five queries you might well see five connections.
But in Oracle what you will always see is 1 connection. In this problem they use
many connections and Oracle supports only 1 connection.Since they use many connections
each page of their web application opens 5,10 connections so server can support 1/5 or
1/10 of concurrent users. So this affects RAM usage also. Altough they have 8 gig of RAM
they can only use 2 gig of RAM.
Problem is solved like this.
Re-architect the design and allow it to take advantage of the fact it was running "on"
Oracle and use a single connection o generate a page. As it is seen Not Understanding Oracle cause re-architecturing
which causes waste of time and money.
|
