Beruflich Dokumente
Kultur Dokumente
In context to Telco world, new customer addition / usage is surged because of new
technologies leads to cost reduction, new products innovation. This exponentially increase
business volume.
Modern day technologies like ‘Data Science ‘ , ‘Data Analytics’ & ‘Revenue Assurance
Systems’ demands more retention duration than before for better processing to arrive very
accurate customer needs or gain business advantages.
Companies having Global presence faces huge challenges in terms of data retention.
Each country demands its own data retention policy, in many cases it is up to 2 years.
Companies are moving towards building single operational stacks to reduce software
development, maintenances & operational costs. This can be achieved by moving all global
customer data processing into single platforms. This leads to huge data
accumulation/processing in single databases.
How to overcome modern day performance issues?
Even though, Oracle database is very robust ORDBMS designed considering all
objective of modern era business. These benefits will be inherited only when we adopt right
features for each of the performance issues.
Since growing/ frequent change in requirements, it is required design databases with
combination of features to achieve multiple objective and easy to adopt changes with
minimal impacts.
SQL & PLSQL Performance: making use of right Joins, Analytical functions and Bulk
collection.
More on analytical functions https://oracle-base.com/articles/misc/analytic-functions
Performance Gains using Indexes.
Traditionally performance issues are overcome through INDEXES. Indexes are
transparent to transactions, but overhead on resource like CPU, Disk I/o’s.
Below are the typical indexes are choose based on the nature of the application.
B-Tree Indexes
BITMAP indexes
Function Based Indexes
Reverse Key Indexes
Unique Indexes
Index Organized Tables (IOT) **
Foreign key Indexes **
Global & local Indexes**
Global Partition indexes**
** B-Tree Types
To Gain maximum performance, index should be designed with SELECTIVITY of 1. More
on Index selectivity http://www.firebirdfaq.org/faq167/
Above such service configuration suppress RAC load balancing flexibility but resources (CPU/Memory) are
undisturbed due to bad performance of the other node.
BT Examples
BFG server many of customer facing application like GS Portal, Ordering, ticketing, ITSM, NGSD and many of
Inventory management systems AGORA, COT+, SMARTS, GSEDW etc.
Business critical application are always hosted on node-2 and all other inventory management interfaces are
mapped to node-1. This ensure node-2 resources are always reserved for BAU critical applications , not
impacted due to any high resource intensive operation on node-1. This configuration also gives opportunity
stop any interface by stopping particular service, say if AGORA is having issues, we can stop this interface by
stopping AGORA mapped service.