Large I/O

When caches are created, all space is assigned to a 2K pool. This pool can be split to allow the cache to perform large I/O, reading up to eight data pages at once. Since most I/O time is spent performing queueing, seeking, and positioning operations, large I/O can greatly increase performance for queries that scan entire tables or ranges of tables.

SQL Server can also perform large I/O on the transaction log.