Proper Memory Allocation And Calculation Is Prerequisites Of Production Database Deployment

Lack of sufficient memory can easily grant increase to memory contention

. When memory prerequisites of active processes surpass the physical memory available on the system, the system initiates paging that is, moving sections of active processes to disk in order to get back physical memory. At this point, performance starts degrading. Gradually, accessible memory continues to reduce, and in order to handle the deficiency without eliminating processes or crashing, the system starts swapping, that is moving entire processes to disk to reclaim the memory used by them. Nominal paging is not usually an effective indication of memory bottlenecks. With some operating systems some paging is inevitable since they page in and out from free memory to vigorously accommodate the unix file system buffers. Also, swapping throughout certain OS housekeeping operations is usual. When paging and swapping seem excessive, however, then there is certainly a memory bottleneck. Ideally paging should be reduced to the minimum and there should be very little or no swapping.

Also, much depends on user awareness. Paging doesnt present a crisis as long as the IS kernel does a good job of selecting infrequently used pages to move to disk. An entire program doesnt need to be in memory while it runs; only parts of the program those are in use need to be there. Most programs spend most of their time up to 70 percent running a small portion around 15 percent of the code. Accordingly, paging often takes place without being noticeable to users. Performance slightly deteriorates as paging begins. However, this deterioration may be barely noticeable. Yet, as the demand on memory increases, the degradation gets bigger and bigger and performance starts taking a nosedive.

Regular exchange of information as a normal part of the house disturbs the operating system performance. Some processes that are inactive for a specified period of time can be changed in order to preserve the memory. But to overcome the operating system through a permutation to a very unusual memory loss, has a negative impact on the performance almost immediately. This is because all processes are written to disk; the result is often difficult, because all processes are written to disk.

To minimize paging and to prevent the prey, you must either limit the number of active parallel processes or add more memory. In 24 * 7 running database high availability, it is impossible to get downtime to add more memory in the box. It is very difficult to extend the material of this type of server database. That's why we take care of the available memory with the configuration of Oracle database memory and calculating the expected number of sessions in the database. This practice is best for creating new database and the deployment of new application development stage. During this phase of application development, we need to justify these requirements related to memory and the hardware configuration of the production database server before you go to production. Otherwise, the Oracle server affects high degree of memory contention in the environment database directly.

by: Gitesh Trivedi

POST COMMENT

Tours And Safaris In Tanzania Tricks And Tips For Writing A Great Cv Travelrecipes Offers Discounted Hotels And Accommodation Green Tea - The Secret To Make Your Skin Look Fresher And Younger White Tea: Health Benefits And Purity Of Taste Iran And Russia Hold Nuclear Talks Kimmy Kardashian And Her Tapes Bikes And Their Accessories Chinese Language Courses Homes Unit Repairs And Maintenance Organisation Likely Will Engage In More Car Insurance Tips And Help E Cigarettes And Places To Buy Them Purchase Paintball Gun Packages And Save Money And Time Tinkerbell Costume And Tinkerbell Party Goods