20.02.2013 Views

A Practical Hardware Sizing Guide for Sybase IQ

A Practical Hardware Sizing Guide for Sybase IQ

A Practical Hardware Sizing Guide for Sybase IQ

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

size of a page. As the page size increases, so does the block size. A data page of 128KB may<br />

compress to a single 8KB block. A 256KB page with the same data on it will consume 16KB on<br />

disk.<br />

Memory use won't increase or decrease as the page size is changed, per se, as the main and<br />

temporary caches are still the same size. If the memory that <strong>IQ</strong> can reference in its caches isn't<br />

increased, though, per<strong>for</strong>mance may suffer.<br />

A system with just a handful of users will, more than likely, not experience as many issues<br />

related to undersized memory as those environments with a lot of concurrent users.<br />

As concurrency increases, the number of pages that are in use will increase in both main and<br />

temporary cache. When moving to a larger page size (<strong>for</strong> instance, doubling from 128 KB page<br />

to 256 KB page) the number of pages that can be stored in the same amount of RAM is cut in<br />

half.<br />

If a user is referencing a fraction of the data on a page more pages will need to be brought in to<br />

handle the query. Should the amount of RAM dedicated to the caches not be increased, a<br />

burden will be added to the system that can <strong>for</strong>ce pages that are the least recently used to be<br />

flushed out to disk be<strong>for</strong>e the new data can be brought into RAM. To properly handle the same<br />

number of users with a doubled page size, it is possible that the <strong>IQ</strong> cache sizes need to be<br />

doubled in size.<br />

Should the page size be changed solely on the number of rows in the table, memory contention<br />

and a possible increase in disk activity can follow. Typically, systems with larger objects have<br />

more memory available and thus don‟t suffer from the impacts. If the RAM sizes don‟t change<br />

over time and the tables are expected to grow to the point where the rowcount sizing would<br />

<strong>for</strong>ce a larger page size, it is recommended that the page size increase be thought through as<br />

possibly disregarded.<br />

Versioning is one aspect that is often overlooked as it relates to page sizes. The number of<br />

pages needed to track versions won't change; it is the amount of cache or disk that would<br />

increase. If one were to double the page size, the amount of cache or storage needed <strong>for</strong><br />

versions would also double.<br />

Final<br />

36

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!