Home > Articles > Web Services

  • Print
  • + Share This
This chapter is from the book

Sizing the Buffer Cache

Data skew and access patterns vary considerably between workloads, making it difficult to predict caching behavior. Consequently, sizing buffer caches is a challenging exercise. As a simple rule of thumb, some people suggest sizing the buffer cache as a proportion of the size of the database. I have read recommendations ranging from 1% to 20% of total database size; the variation in these recommendations highlights the degree of difficulty involved in such a sizing.

Some time ago, Performance and Availability Engineering conducted a study to better understand the relationship between cache sizes and hit rates and the impact of both on performance. As we will see, the optimal buffer cache size was between 10% and 15% of the database size for the workload used in the study.

The TPC-C schema and workload provided the test environment, and DB2 for Solaris was used as the test database.

The investigation was divided into two phases. In the first phase, the number of CPUs was held constant while the database size and the buffer cache size were varied. In the second phase, the number of CPUs was varied while the buffer cache size and database size were held constant.

Measurements were taken with buffer cache sizes ranging from 199 Mbytes to 3.1 Gbytes, and database scales of 100 (equivalent to 8.7 Gbytes), 250, 375, 425, and 525 (equivalent to 45.7 Gbytes).

The findings of the study included the observations outlined in the following sections.

Influence of Buffer Cache Size on Throughput

Transaction throughput is dependent on the ratio of the database size to the buffer cache size. When the buffer cache is small relative to the size of the database, throughput is far below the peak value achievable for the configuration. Figure 7.1 shows the relationship between the throughput and the size of the buffer cache.

Figure 7.1 Throughput versus buffer cache size

As the buffer cache is gradually increased in size, throughput rises steeply at first, then reaches a "knee point," after which it continues to increase, but at a greatly reduced rate. The 100 scale curve clearly shows this phenomenon: as the buffer cache increases from 50,000 to 300,000 pages, the throughput increases rapidly. Beyond that point, large increases in the size of the buffer cache only yield small gains in throughput. Larger databases (scale 250 and above) also exhibit this behavior.

The 525 scale result highlights another key characteristic: as buffer cache sizes grow, it takes more memory to achieve the same throughput increase. In this case, the throughput at 200,000 buffers doubled as the cache increased by another 200,000 buffers, but beyond 400,000 buffers, it took twice as much memory (400,000 buffers) to increase the throughput by the same amount again.

Figure 7.1 also clearly demonstrates that smaller databases benefit more than larger databases when a small buffer cache is increased in size. This behavior may seem counterintuitive, but it results from the fact that a high proportion of a small database can be cached quickly, whereas the same memory increase caches a small proportion of a large database. At the same time, the growth in the throughput slows much more quickly for small databases, whereas the benefits continue for larger databases. In every case, a point of diminishing returns is eventually reached, beyond which further increases in buffer cache size yield diminishing benefits.

The study demonstrated that, for this workload, the optimal buffer cache size is between 10% and 15% of the database size. Table 7-1 shows the buffer cache sizes required to reach the "knee point," the point beyond which further cache size increases result in diminishing returns.

Table 7-1 Buffer size and data hit rate at knee points


Buffer Size (Gbytes)

% of Database Size

Data Hit Rate

















Results for larger database scales are not reported since the knee point was not reached (larger buffer caches would have been required). Note, too, that the cache hit rate shown in the table applies only to data pages (DB2 for Solaris separately reports cache hit rate statistics for data pages, index pages, and all pages).

As Table 7-1 shows, the smaller databases used slightly larger proportions of buffer cache memory to reach their knee points.

A more recent study on a different hardware platform with a different database suggested an optimal buffer cache size of between 5% and 10% of the database size. The difference between these results and those from the earlier study demonstrates that no single answer fits all situations.

Influence of Buffer Cache Size on Data Cache Hit Rate

Figure 7.2 shows the relationship between the data cache hit rate and the buffer cache size.

Figure 7.2 Data cache hit rate versus buffer cache size

As with throughput, the data cache hit rate initially climbs steeply as the buffer cache increases in size, then reaches a knee point and gradually settles onto a plateau. As before, the 100 scale test illustrates the behavior most clearly, whereas the larger database sizes needed more memory to reach the cache hit rate upper limit.

The practical limit to the data cache hit rate for this workload was around 98%. The overall cache hit rate was higher, though; including the index cache hit rate in this figure would have increased the upper limit to around 99% since the index cache hit rate was consistently higher than the data cache hit rate.

Further tests confirmed that the behavior described for 12 CPUs also applied to 4 and 8 CPUs.

In concluding this discussion, it is worth noting that the memory capacities of Sun servers have increased significantly in recent years, a trend that is likely to continue. Although systems with 1 Gbyte of memory per CPU were typical in the past, current generation systems ship with 4 or 8 Gbytes per CPU. Larger memory configurations, combined with 64-bit databases on 64-bit Solaris, should allow buffer caches to be sized generously.

Influence of Page Size on Buffer Cache Effectiveness

Choosing the database page size (or block size) has important implications for performance of the database. Larger page sizes are usually chosen for DSS applications since they reduce overhead when large volumes of data are sequentially processed. Smaller page sizes are usually chosen for OLTP databases since I/O access tends to be random and row sizes relatively small.

One of the main reasons why the database page size impacts performance is due to its influence on the effectiveness of the database buffer cache. The page size determines both the size of pages in the buffer cache and the size of I/Os to and from the database tables on disk.

Consider a table with an average row length of 500 bytes: up to four rows can be accommodated in a 2-Kbyte page. The unit of database I/O is the page size, so every time a row is read into the buffer cache on behalf of an application, up to three other rows will accompany it. If the other three rows are required at the same time by that application or by other users, the buffer space is being used effectively and future I/Os will be saved. If the I/O access is random, though, then the other three rows are unlikely to be used.

The key issue here is access locality: locality of data access is high if data that is physically contiguous is accessed at or around the same time. Remember that in most cases, data is not stored in any particular order within a database table, so locality of access is hard to predict (although for some types of clustered index, data is stored in key sequence). When an entire table is scanned, such as for batch jobs or DSS queries, effective access locality is high since all rows will be processed within each page.

By contrast, up to 64 of the 500-byte rows can be accommodated in a 32-Kbyte page. If access locality is high and most or all of the other 63 rows can be used at the same time, many I/Os have been saved.

Large pages are the worst-case scenario, though, where data access is random and access locality is low. With 32-Kbyte pages, for example, each time a 500-byte row is read or written, a 32-Kbyte I/O must be completed. Worse still, for a buffer cache 2 Gbytes in size, the number of available 32-Kbyte buffers is only 65,536, compared to 1,048,576 buffers with 2-Kbyte pages. So fewer pages can be cached, while little benefit is derived from the large number of rows carried along with each page.

Very large buffer caches with 64-bit databases introduce other considerations. A 32-Gbyte buffer cache, for example, will support 16,777,216 pages 2 Kbytes in size and 1,048,576 pages 32 Kbytes in size. The overhead associated with managing the buffer cache increases as the number of pages increases. Consequently, a point will probably be reached beyond which it is more efficient to deal with fewer large pages.

To summarize, use smaller page sizes (2 to 8 Kbytes) for OLTP applications to maximize the effectiveness of the cache for randomly accessed data. Use larger page sizes for DSS applications to reduce the number of pages involved during access to large tables.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020