A new look-up-table memory predistorter for power amplifier with memory effects is proposed.
针对有记忆非线性功放提出了一种新的基于查找表的记忆型预失真器。
The sweetest memory of my childhood is about a round table.
我童年最温馨的记忆是关于一张圆桌。
Table 11 shows the memory usage for different types of loads.
表11展示不同类型工作负载的内存使用情况。
Table 2 lists the default memory model configuration for different ranges of heap size.
表2列出了不同堆大小范围的默认内存模型配置。
Table 3 shows the memory usage for different types of loads.
表3显示了不同的负载类型情况下的内存使用情况。
In this method, one of the tables, usually the smaller one, is scanned and used to create a hash table in memory.
在该方法中，需要扫描其中的一个表，通常扫描较小的那个表，用它在内存中创建一个哈希表。
Agent private memory is affected by the database configuration parameters shown in Table 5.
代理程序私有内存受表5中所示的数据库配置参数的影响。
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.
对于这个报告，你需要显示每个用户当前的内存使用情况图，然后在一个表中按照每个会话将内存使用划分。
Instead, use an in memory hash table to cache the data and just keep a key to the data in the session.
相反地，应该使用内存中的哈希表来缓存数据，并且在会话中保存一个对此数据进行引用的键。
This helps ensure the data for this table is continuously cached in memory.
这有助于确保此表中的数据连续地缓存在内存中。
The field for shared memory used in the table shows about 3 GBs of memory for both tests.
在这个表中，“所使用的共享内存”字段说明这两个测试都使用了大约3GB 的内存。
Table 5 shows memory usage for different types of loads.
表5展示各种负载的内存使用情况。
All network devices have an ARP table, a short-term memory of all the IP addresses and MAC addresses the device has already matched together.
所有的网络设备都有一个ARP映射表，就是内存里的一小段存储着目前该设备已经匹配的IP地址和MAC地址对。
This allows the entire lookup table to be loaded into memory each time a user submits a request to read or write data.
在用户每次提交一个读写数据的请求时，这可以将要查询的整个表装入内存中。
Table 1 (in Figure 7) shows the size of the page table space allocated based on the maximum partition memory value.
表1(在图7中)显示了基于最大分区内存值来分配的页表空间大小。
However, as the table grows, the RUNSTATS command takes more time, CPU and memory resources to complete.
然而，随着表的增长，完成RUNSTATS命令将占用更多时间、CPU和内存资源。
As physical memory on today's workstations get larger and larger, the table used for memory translation must consume more and more resources to map the working memory set.
随着当今工作站上的物理内存越来越大，用于内存转换的表必须消费越来越多的资源，以映射工作内存集。
The user space memory access functions to be explored are listed in Table 1.
用户空间内存访问函数在表1中列出。
Examples of operations that use the sort heap include hash joins and operations where the table is in memory.
使用排序堆的操作示例包括内存中表的散列连接和操作。
Also watch the way the memory command table is being accessed on both sides in Listing 5.
还要注意清单5中从两边访问内存命令表的方法。
A TLB miss requires accessing a page table that is stored in the main memory, which consumes considerably more processor cycles.
如果TLB没有命中，那么就需要访问存储在主存中的页表，而这样做需要消耗相当多的处理器周期。
A fixed number of processes can be attached to pkcsslotd, so a static table in Shared memory is used.
固定数量的进程可以被附加到pkcsslotd，因此将使用共享内存中的一个静态表。
Table 1 lists the memory limits for each of the DB2 memory sets.
表1列出了每种DB 2内存集的限制。
This first table shows the results of having no Domino memory Settings enabled.
第一个表显示没有启用Domino内存设置时的结果。
The snippet processor reads table data from the disk array into memory.
snippet处理器将表数据从硬盘阵列读取到内存中。
HSQLDB keeps all table and index data in memory, saving all SQL statements issued into a file named database.script, which also ACTS as the transaction log.
HSQLDB将所有表和索引数据放在内存中，将所有发出的sql语句保存到一个名为database .script的文件中，该文件同时也充当着事务日志的角色。
The POWER Hypervisor performs virtual memory management using a global partition page table, and manages any attempt by a partition to access memory outside its allocated limit.
POWER Hypervisor使用全局分区页表执行虚拟内存管理，并管理分区尝试访问超出其分配限制之外的内存的请求。
At least 40mb of memory for the default configuration, plus space for each table you intend to place in memory.
默认配置需要至少40MB内存，在内存中保存的每个表需要额外的空间。
Table 1 - DB2 memory set limits based on 32-bit memory structure.
表1-基于32位内存结构的DB 2内存集限制。
Table 1. DB2 memory set limits based on 32-bit memory structure.
表1 -基于32位内存结构的DB 2内存集限制。
应用推荐