Examples with "access to the buffer cache" and their translation in Japans
We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
Before data stored in the database can be queried or modified, it must be read from a disk and stored in memory in the buffer cache. All user processes connected to the database share access to the buffer cache. For optimal performance, the buffer cache should be large enough to avoid frequent disk I/O operations.
The kernel components take responsibility for such things as the scheduling of processing activity, synchronizing access to shared data structures, physical memory allocation, and buffer cache management.
All of the Linux file systems use a common buffer cache to cache data buffers from the underlying devices to help speed up access by all of the file systems to the physical devices holding the file systems.
すべての Linux ファイルシステムは、共通のバッファキャッシュを利用して、基礎となるデバイスのデータバッファをキャッシュする。 これは、ファイルシステムが、そのファイルシステムを保持する物理デバイスにアクセスする際、アクセス速度の向上に役立つ。
This wait happens when a session wants to access a database block in the buffer cache but it cannot because the buffer is busy. Another session is modifying the block and the contents of the block are in flux during the guarantee that the reader has a coherent image of the block with either all of the changes or none of the changes, the session modifying the block marks the block header with a flag letting other users know a change is taking place and to wait until the complete change is applied.
Columnar compression provides significantly higher compression ratios as compared to previously available compression features of Oracle also has a higher CPU cost both at load time and at access time. Due to higher compression ratios, data consumes less space in the buffer cache, providing I/O benefits that offset the CPU costs. The overhead is relatively low for full table scans than for single row access.
Use the Total Transfer by Instance page to view the number of logical reads that read data from the buffer cache of other instances through Direct Memory Access and from disk. This essentially profiles how much work is performed in the local buffer cache, rather than the portion of non-local references that incur some latency overhead.
≪インスタンスごとの転送合計|Total Transfer By Instance|emdw≫・ページを使用して、ダイレクト・メモリー・アクセスを経由して他のインスタンスのバッファ・キャッシュからデータを読み取る論理読取り、およびディスクからデータを読み取る論理読取りの数を表示します。これは、待機時間のオーバーヘッドの原因であるローカル参照以外の部分ではなく、ローカル・バッファ・キャッシュにおける処理量のプロファイルです。
The testing device comprises a test executing unit for executing a test of the object device, a fail memory, to which an interleave technology for multiplexing an access to a plurality of banks is applied, for storing a test result by the test executing unit, a buffer memory such as a memory, to which the interleave technology is not applied, or a memory, which has a smaller bank number than that of the fail memory although the interleave technology is applied thereto, for storing the test result stored in the fail memory and transferred thereto, a cache memory having a shorter random access time period than that of the buffer memory, for storing at least a portion of the test result stored in the buffer memory and transferred thereto, and an analysis unit for analyzing at least a portion of the test result stored in the cache memory.
Effective use of the buffer cache can greatly reduce the I/O load on the the buffer cache is too small, frequently accessed data will be flushed from the buffer cache too quickly which forces the information to be re-fetched from disk. Since disk access is much slower than memory access, application performance will suffer. In addition, the extra burden imposed on the I/O subsystem could introduce a bottleneck at one or more devices that would further degrade performance.
Shows the percentage of logical read operations that retrieved data from the buffer cache of other instances by way of Direct Memory Access and from disk. It is essentially a profile of how much work is performed in the local buffer cache, rather than the portion of remote references that incur some latency overhead. Click the legends to the right of the chart to go to the Global Cache Block Transfers vs. Logical Reads by Instance and Physical Reads vs. Logical Reads by Instance pages. From there, you can click an instance legend under the chart to go to the Segment Statistics by Instance page, where you can see which segments are causing cache contention...
ダイレクト・メモリー・アクセス経由で他のインスタンスのバッファ・キャッシュからデータを取得した論理読取り操作と、ディスクからデータを取得した論理読取り操作の割合が表示されます。これは実質的には、待機時間のオーバーヘッドを発生させるリモート参照の割合ではなく、ローカル・バッファ・キャッシュで実行される処理の割合を表します。グラフの右にある凡例をクリックすると、インスタンスごとのグローバル・キャッシュ・ブロック転送と論理読取りに関するページおよびインスタンスごとの物理読取りと論理読取りに関するページに移動します。ここでグラフの下にあるインスタンスの凡例をクリックすると、≪インスタンスごとのセグメント統計|Segment Statistics By Instance|emdw≫ページに移動できます。このページでは、どのセグメントでキャッシュ競合が発生しているかを確認できます。
Potentieel gevoelige of ongepaste informatie
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.