Be Careful In Usage Of Processor Affinity On The Database Server

Be Careful In Usage Of Processor Affinity On The Database Server

By:


Cache affinity processor affinity is the binding process to a specific processor. Historically, the presumption is that when a particular CPU is running a process that is a good chance that the process would be beneficial if it is run on the same processor next time. Specifically, it is assumed that the process will be able to reuse the data in the CPU level 1 cache and thus avoid having to read physical memory. For Oracle the most modern, but it is rarely true. This is because the CPU L1 cache is too small to store anything of real value. Furthermore, no performance advantage (perhaps a few nanoseconds) derived negligible. Newer uniprocessor and SMP machines are implementing shorter buses linking the CPU to physical memory. Therefore, access to physical memory is incredibly fast now.

However, technical experts and gurus of some sites insist on using the processor affinity to improve performance. What they end up getting in return is increased administrative costs and performance degradation. Since joining forces the CPU of a process to use some CPU, the process will have to wait or sleep if the processor becomes busy executing another process. While the other processors are available at the time, the process cannot be handled by them. These scenarios are very common in sites running OLTP and DSS applications.

In trying to reduce the level of system load, do not to resort to methods that can hinder the performance level in place and use of resources.

At various times, all that we meet people who tend to run big questions during the hours of peak production and are often the first to complain about the performance. This is more common in firms with DSS systems such as data warehouses and data marts. Somehow, he ended work that has been designed to work late into the night to fill the warehouse into service during peak morning and early afternoon hours. Make sure to detect and prevent such a lack of production tasks or mission critical to valuable resources such as memory and CPU.

Therefore, we can say that if we enable processor affinity or CPU affinity then in future our database server may be affecting with mysterious performance problems. For preventive future performance bottleneck we need to eliminate more usage of processor affinity. Oracle database uses own memory cache called System Global Area as SGA. Oracle database is strongly maintaining this SGA for preventing disk I/O and physical reads.

About the Author:
About Author:Gitesh Trivedi has 14+ years of experience and providing
Remote Oracle Support and also author of online Oracle Trainings courses.



Article Originally Published On: http://www.articlesnatch.com


Tags: , , , ,

|

Loading...
Related....
Videos...

Recent Software Articles

Comments

Still can't find what you are looking for? Search for it!

Loading

Site Navigation:

Copyright 2005-2011 ArticleSnatch, LLC - All Rights Reserved.
Privacy Policy | Terms of Service.