In our scenario, the systems we are using are identical in terms of disk drives, directory structure, database driver location, and so on.
在我们的场景中，所使用的系统在磁盘驱动器、目录结构、数据库驱动程序位置等方面都是完全相同的。
In summary, elastic data grids improve hardware utilization, reduce costly redundant transactions, and eliminate the need for a high speed disk and database used for persistence.
总之，弹性数据网格提高了硬件利用率，减少了昂贵的冗余事务，消除了用于持久性的高速磁盘和数据库的必要性。
The constraining factors for performance are the number of concurrent database connections and available memory (both RAM and disk) in relation to incoming data volume.
性能的限制因素是关于进入的数据量的并发数据库连接的数量和可用内存(RAM和磁盘)。
A checkpoint refers to a point when the database server synchronizes the pages on disk with the pages in the shared-memory buffers.
检查点是指数据库服务器在特定的时间点对磁盘上的页面和共享内存缓冲区中的页面进行同步。
It'll never be as fast to store things in a stable database format on disk as to keep them only in memory, but there's still plenty of room to speed things up.
以稳定数据库格式将数据存储在磁盘上永远都不会像把它们存储在内存中那样快，但存储速度仍然有很大的提升空间。
Disk usage in the analysis database: What artifacts are created during the execution of a rule?
分析数据库中磁盘使用：在规则执行过程中创建了什么项目？
Finally you've seen the types of data that are generated during each execution in the analysis database, and how you can reduce disk utilization.
最后，看到了在分析数据库中每次执行成功所生成的数据类型，以及如何降低硬盘使用量。
Here are some techniques for avoiding long-running actions in the UI thread, using a common example: a table or tree that is filled from some sort of database query, network call, or disk.
有一些技术用来避免UI线程中的长时间运行动作，举一个常见的例子：使用某种数据库查询、网络调用或磁盘进行填充的表或树。
A smaller number of changed objects per transaction mean more commits to your database, each of which incurs some disk-related overhead as mentioned in Section 4.5.
每次事务修改的对象数量越少就意味着会有更多数据库提交，正如4.5节所述每次提交都会带来磁盘相关的开销。
These page cleaners write changed pages from the buffer pool to disk before the space in the buffer pool is required by a database agent.
在数据库代理程序需要缓冲池中的空间之前，这些页清除程序将缓冲池中已更改的页写到磁盘。
Database clustering places frequently accessed DB2 rows in the same page and frequently accessed pages close together on disk.
数据库集群会将经常访问的DB 2行放在同一页面中，经常访问的页面集中放在磁盘上。
Along with the shift in hardware away from disk-centric and toward memory - and processor-centric data management, flexible technologies are being developed to address different database workloads.
除了硬件从以磁盘为中心转移到以内存和处理器为中心的数据管理外，一些用于解决不同数据库工作负载的灵活的技术也在开发中。
Numerous repeated tests, found a database that used to take about 6 G disk Spaces to store backup files in IDS 9.21 now it takes only 5 G in IDS 9.40; this saves 1 G of disk space with new IDS.
无数重复实验发现，过去在IDS 9.21中要使用6g磁盘空间存储备份文件的数据库，在IDS 9.40中仅需使用5 G即可；这样，使用新的IDS节省了1 G的磁盘空间。
Well, maybe it didn't exactly happen that way, but IBM has been involved in some of the biggest database developments of the past 50 years. It all began in the era of punch CARDS and disk platters.
确切地说，也许它并不是以这种方式产生的，但是IBM在过去50年参与了最大的数据库开发，而这一切都是从卡带和磁带时代开始的。
The typical database sizes (in terms of occupied space on the disk) for SOA/BPM production databases are a small fraction of the space (in terms of number of disk drives) needed for good performance.
SOA/BPM生产数据库的典型数据库大小（就磁盘上的占用空间而言）是良好性能所需的空间（就磁盘驱动器数量而言）的一小部分。
The database server writes data stored in a blobspace directly to disk.
数据库服务器将存储在blobspace中的数据直接写入到磁盘。
SQLite supports databases of up to 2 TB, with each database stored entirely in a single disk file.
SQLite支持大小高达2TB的数据库，每个数据库完全存储在单个磁盘文件中。
Doing so creates a database on disk called test.tdb and opens it so that any changes you make in this session will be on that file.
这样做可以在磁盘上创建名为test . tdb的数据库并打开它以便您在此会话中进行的任何变更都在该文件上。
All this information is encapsulated in an ST_Geometry value, implying that this value also needs about one MB disk space in the database.
所有信息封装在一个st_geometry值中，这意味着这个值在数据库中也需要大约1MB的磁盘空间。
The Database System Administrator (DBA) faces a number of challenges in managing the disk space allocated to an Informix server.
DatabaseSystemAdministrator (DBA)在管理分配给Informix服务器的磁盘空间时面临大量挑战。
Increased disk utilisation also occurs if events and actions require access to a user database (for example, database fetches in intermediate objects for event and action augmentation).
事件和动作需要访问用户数据库还会导致磁盘使用率增加(例如，数据库获取中间对象导致事件和动作增加)。
This is not just some transient in-memory database; it is persisted to disk.
这不仅仅是临时的内存中的数据库；而是永久保存在磁盘中。
The database session stores these query logs in memory and periodically commits the local history to disk.
数据库会话在内存中保存这些查询日志，并定期将本地历史写入磁盘。
All database tables and indexes are kept in memory and never saved to disk.
所有数据库表和索引都放在内存中，而且永远不会保存到磁盘上。
Perform the disk failover such that database processing can continue at the primary site, as shown in Listing 18.
执行磁盘的故障转移以便数据库处理能够在主站点继续，如清单18所示。
As the name implies, an in-memory database resides entirely in main memory rather than on disk, making data access an order of magnitude faster than with conventional, disk-based databases.
顾名思义，内存中数据库完全驻留在主存中，而不是磁盘上，这使得数据访问比传统的基于磁盘的数据块要快一个数量级。
A database complicates the matter, because it caches some disk writes, which may result in an inconsistent snapshot.
数据库使问题复杂化，因为它缓存了一些磁盘写操作，这可能会生成一个不一致的快照。
Page cleaners, on the other hand, write changed pages from the buffer pool to disk before the space in the buffer pool is required by a database agent.
另一方面，数据库代理需要缓冲池中的空间之前，页面清洗器将已修改的页面从缓冲池写入磁盘。
Page cleaners, on the other hand, write changed pages from the buffer pool to disk before the space in the buffer pool is required by a database agent.
另一方面，数据库代理需要缓冲池中的空间之前，页面清洗器将已修改的页面从缓冲池写入磁盘。
应用推荐