例如，NDB存储引擎支持分区表，内存引擎支持内存表。
For example, NDB storage engine supports partitioned tables and memory engine supports in-memory tables.
该方法结合内存表和磁盘表两种机制，不但提供快速的性能，而且解决了内存表的永久保存问题。
This method combines memory-based table with disk-based table, it not only provides good performance, but also solves the problem of memory table's permanent storage.
TClientDataSet 只是在客户端的一个内存表（in-memory table），对该数据集的更改将不会自动保存。
The TClientDataSet is only an in-memory table at the client side, and changes to this dataset will not be saved automatically.
在32 位机器上页表通常只可以存储在低端内存中。
Page-tables can normally be stored only in low memory on 32-bit machines.
处理较宽的表也需要更多的内存。
相反地，应该使用内存中的哈希表来缓存数据，并且在会话中保存一个对此数据进行引用的键。
Instead, use an in memory hash table to cache the data and just keep a key to the data in the session.
在这种情况下，每个映射到同一块1GB内存的进程将为页表条目付出自己2MB的代价。
In such a situation, every process mapping that same 1 GB of memory would consume its own 2 MB worth of page-table entries.
表5.影响应用程序共享内存的配置参数。
Table 5. Configuration parameters that affect application Shared memory.
它们将自动被合并在一起来生成一个单一的内存路由表。
They will automatically be merged to create a single in-memory route table.
代理共享内存受表4中所示的数据库和数据库管理器配置参数的影响。
Agent Shared memory is affected by the database and database manager configuration parameters shown in Table 4.
为提高性能，从磁盘读取的样式表缓存在内存中——节点不能缓存输入消息提供的样式表。
To improve performance, stylesheets read from disk are cached in memory - the node does not cache stylesheets that are supplied in the input message.
代理程序私有内存受表5中所示的数据库配置参数的影响。
Agent private memory is affected by the database configuration parameters shown in Table 5.
表5展示各种负载的内存使用情况。
还要注意清单5中从两边访问内存命令表的方法。
Also watch the way the memory command table is being accessed on both sides in Listing 5.
用户空间内存访问函数在表1中列出。
The user space memory access functions to be explored are listed in Table 1.
在高端内存中存储页表条目。
MySQL也会分配一些内存来读取表。
Pacifica还可以使用宿主和客户内存管理单元(MMU)表来进行地址转换。
Pacifica also amends address translation with host and guest memory management unit (MMU) tables.
它使用一种有效的算法压缩仓库表并将它们存储在内存中。
It compresses warehouse tables with an efficient algorithm and stores them in memory.
不过，对于那些在大量进程在运行的系统来说，将页表存储到高端内存中可以在低端内存区域挤出更多的内存。
However, for systems in which a large number of processes are running, storing page tables in high memory can be enabled to squeeze more memory out of the low memory area.
虚拟内存到物理内存的映射通过页表完成，这是在底层软件中实现的(见图1)。
The mapping of virtual memory to physical memory occurs through page tables, which are implemented in the underlying hardware (see Figure 1).
对于这个报告，你需要显示每个用户当前的内存使用情况图，然后在一个表中按照每个会话将内存使用划分。
For this report, you want to display a graph of total memory usage per user and then, in a table, break that memory usage down on a per-session basis.
这些统计信息存储在表示声明的临时表的目录信息的内存结构中。
These statistics are stored in memory structures that represent the catalog information for declared temporary tables.
操作系统通过一个内部表将处理器地址空间中的内存段映射到内存页，该表定义哪些内存段由哪些处理器所拥有，等等。
Operating systems map memory segments in a processes' address space to memory pages through an internal table which defines what memory segments are owned by what processes, and so on.
在该方法中，需要扫描其中的一个表，通常扫描较小的那个表，用它在内存中创建一个哈希表。
In this method, one of the tables, usually the smaller one, is scanned and used to create a hash table in memory.
在构建阶段，数据库服务器读取一个表，并且在应用所有现有筛选器之后，在内存中创建一个哈希表。
In the build phase, the database server reads one table, and, after it applies any existing filters, it creates a hash table in memory.
很多编译器通过将表放入只读内存中可以生成更高效的代码。
Many compilers can generate more efficient code for this by putting the tables in read-only memory.
在用户每次提交一个读写数据的请求时，这可以将要查询的整个表装入内存中。
This allows the entire lookup table to be loaded into memory each time a user submits a request to read or write data.
在这个例子中，值列表被放在内存中的一个表中。
The list of values is put in a table in memory in this case.
虽然在第一行中，针对引擎的大小来对内存做了考虑(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.
应用推荐