Nu am putut găsi această intrare. Se afișează rezultate aproximative. Verificați ortografia sau propuneți adăugarea acestui termen în dicționar.
パラレル実行サーバー
This parameter controls the number of preparer servers a capture uses. Each reader server, preparer server, and builder server is a parallel execution server, and the number of preparer servers equals the number specified for the parallelism capture process parameter. So, if parallelism is set to 5, then a capture process uses a total of seven parallel execution servers, assuming seven parallel execution servers are available: one reader server, five preparer servers, and one builder server.
The reader server for an apply process dequeues messages from the queue. The reader server is a parallel execution server that computes dependencies between LCRs and assembles messages into transactions. The reader server then returns the assembled transactions to the coordinator, which assigns them to idle apply servers.
A component of a capture process that scans a region defined by the reader server and performs prefiltering of changes found in the redo log. A reader server is parallel execution server, and multiple reader servers can run in parallel. Prefiltering entails sending partial information about changes, such as schema and object name for a change, to the rules engine for evaluation, and receiving the results of the evaluation.
Executions - Shows how many times an operation was executed. Operations in the execution plan can execute multiple times when they are parallel (at least once per parallel execution server) or when they are restarted. For example, a "NESTED-LOOP JOIN" operation restarts its inner input as many times as the number of rows coming from its left input. Similarly, a "PARTITION" operation restarts its underlying full table scan operation as many times as partitions in the table are being scanned.
Parallel execution server number of the apply server
適用サーバーのパラレル実行サーバー番号
The next level shows statistics aggregated by each type of parallel execution servers: parallel coordinator, parallel set 1, and optionally parallel set 2 for more complex execution plans, where the two sets of servers are working in parallel as a pipeline. The final level of the hierarchy shows the statistics associated with individual parallel execution server processes within each parallel set.
If the execution is parallel, the graph shows the activity for all sessions involved in the parallel execution. This includes the user session, which acts as a coordinator for the parallel execution, and one session for each parallel execution server process.
If the execution is cross-instance, a check-box shows (respectively hide) the instance level from the hierarchy. Not showing the instance level in the hierarchy enables you to easily see the statistics for all parallel execution servers within a set. Ideally, for good scalability of the parallel execution, it is expected that the query coordinator performs a negligible amount of work. Also, the execution should present a minimal amount of skew; each server within a parallel set should perform about the same amount of work. On the other hand, statistics between the two sets of parallel execution server processes are expected to be different, because the two parallel sets are processing different operations of the execution plan.
Exemplele au rolul de a te ajuta să traduci cuvinte sau expresii corect si adaptat la context. Nu sunt selectate sau validate manual, așadar pot conține termeni inadecvați. Te rugăm să raportezi exemplele pe care le consideri inadecvate. Traducerile vulgare sau colocviale sunt în general marcate cu roșu sau cu portocaliu.