第二个改动是加入另一个直写式行缓存，它包含了数据库记录：用户和tweets。
The second change was adding another write-through Row Cache containing database records: users and tweets.
如果我们指定完全缓存或者行缓存，buf和size可选的指定一个buffer和它的大小。
If we specify fully buffered or line buffered, buf and size can optionally specify a buffer and its size.
虽然这种替代方法更简单，但并不具备细节控制能力。因为这两种方法处理行缓存的方式不同，千万不能搞混。
The alternative approach is simpler but does not provide as fine-grained control. Since the two approaches manage line buffering differently, they should not be mixed.
第四行以超出锁的次数、用户线程或者缓存数来开始(通常所有的0会是这样)。
The fourth line starts with the number of times we have exceeded locks, user threads or buffers (all 0 and should generally be so).
当所有行处理完成之后，将完全更新缓存，并且所有相关的赋值操作符都对齐到一个合适的列。
Once all the lines have been processed, the buffer will have been completely updated and all the relevant assignment operators aligned to a suitable column.
接下来的一行将准备缓存选项。
此参数指定在将数据发送给加载驱动程序之前应该缓存多少行。
This parameter specifies how many rows a connector should cache before the data is sent to the load driver.
不要缓存数据库行或文件
虽然在第一行中，针对引擎的大小来对内存做了考虑(118,812KB)，但是，我们没有使用很多内存，我们为表保持缓存。
Although looking one line higher at the size of the engine in memory (118,812 KB), we aren't working with a lot of memory, Let's keep cache on the table.
直接使用SQL会使缓存出问题，因为缓存层必须处理完整的结果集，而不是单独一个数据库行。
Directly using SQL makes caching problematic, since the caching layer must deal with full result sets rather than single database rows.
它采用的方法是从DB 2日志(常常是从非常快速的日志内存缓存)中获取读者事务需要的数据行。
It works by retrieving the data row information that the reader transaction needs from the DB2 logs-usually from the log's memory cache, which is very fast.
下一行告诉我们尽管有 231MB 内存正在使用，但是应用程序只使用了其中的 86MB；缓冲区和高速缓存使用了其余的内存。
The next line shows us that while 231MB is being used, only 86MB of this is actually being used by applications; the rest is being used for buffers and cache.
一行后面的资源不缓存，且仅在联网时可访问。
Resources following the network: line are not cached and can be accessed only when the network is available.
通过将标准网格视图换成缓存视图，只改了一两行代码，程序运行如常。
By swapping out the standard grid view for the buffered view, the application performed as it should by only changing a line or two of code.
虽然可以使用memcached存储加载自数据库的数据行，但这实际上是查询缓存，并且大多数数据库都提供各自的查询缓存的机制。
Although you can use memcached to store the rows of data as loaded from a database, this is really query caching, and most databases provide their own query-caching mechanism.
现在只需使用一行代码，Catalog控制器就能够使用请求端缓存功能来缓存从遗留Catalog应用程序返回的Catalog了。
With one line of code, the catalog controller can now use the requester-side caching capabilities for caching the catalogs returned from the legacy catalog application.
最后的代码块同时遍历原来的缓存行号(linenum)和行列表中的每个行，以重新格式化赋值行。
The final code block then reformats the assignment lines, by iterating through the original buffer line Numbers (linenum) and through each line in the lines list, in parallel.
然后通过调用setline将新的行写回到编辑器的缓存中，并且更新行跟踪以准备下一次遍历。
That new line is then written back to the editor buffer by calling setline , and the line tracking is updated for the next iteration.
使用JDBC扩展包中的行集来缓存结果集；
缓存的地方数据到缓存中的行(也称为块)。
The cache places data into the cache in lines (also called blocks).
既然所有必要的计算都在第一行代码中完成了，那么后两行代码不会产生递归运算，因为直接返回缓存中的数值。
Since all of the necessary calculations are completed on the first line, the next two lines need not perform any recursion because cached values are returned.
当一个缓存行中包含有有效的缓存数据或指令时这个缓存行就是有效的，反之是无效的。
A cache line is said to be valid when it contains cached data or instructions, and invalid when it does not.
当一个缓存行中包含有有效的缓存数据或指令时这个缓存行就是有效的，反之是无效的。
A cache line is said to be valid when it contains cached data or instructions, and invalid when it does not.
应用推荐