Connection Pool in Admin Tool….
(4 votes, average: 4.25 out of 5)
Loading ...I m back again after some gap… Now, lets understand whts connection pool..
The connection pool is an object in the Physical layer that describes access to the data source. It contains information about the connection between the Siebel Analytics Server and that data source.
The Physical layer in the Administration Tool contains at least one connection pool for each database. When you create the physical layer by importing a schema for a data source, the connection pool is created automatically. You can configure multiple connection pools for a database. Connection pools allow multiple concurrent data source requests (queries) to share a single database connection, reducing the overhead of connecting to a database.
For each connection pool, you must specify the maximum number of concurrent connections allowed. After this limit is reached, the Analytics Server routes all other connection requests to another connection pool or, if no other connection pools exist, the connection request waits until a connection becomes available.
A word of caution : Increasing the allowed number of concurrent connections can potentially increase the load on the underlying database accessed by the connection pool.
In addition to the potential load and costs associated with the database resources, the Siebel Analytics Server allocates shared memory for each connection upon server startup. This raises the number of connections and increases Siebel Analytics Server memory usage.
I would like users to share their comments also…
could you be more specific in saying that multiple concurrent data sources request.
Also provide me some information on like we have 2 connection pools for a single database or schema and when a query is issued ,which connection pool does it access and why?
and when does it access the other connection pool.
Multiple concurrent data requests mean that when we run reports in OBIEE, multiple queries get fired and these need to be routed to the Database through the connection pool.
To answer your second question, if you have 2 connection pools for a single Database and when you fire a query then by default it hits the 1st connection pool.
There is a measure in the connection pool saying Allowed number of concurrent connections, which tells the number of requests that can be routed through a connection pool. If the total number of requests(queries from reports) exceeds that measure specified in the connection pool, then, the queries get routed through another connection pool.
Kindly revert back if you have any other questions.
How do we decide the maximum number of concurrent connections allowed per connection pool?
To decide the maximum number of concurrent connections allowed per connection pool you need to know the details of the underlying DB and also need to check with the DBA on the concurrent requests the DB can handle at a point of time. You also need to know the number of people who will be hitting the DB using that connection pool and also need to consider the performance.
If your DB doesnt support many concurrent connections then it might slow down your performance.
Leave your response!
Recent Posts
Categories
Archives
Tags
Most Commented
Most Viewed