对这些Linux组件进行优化(例如2.6版本内核中的新o(1)调度程序)都可以让系统管理程序(主机操作系统)和Linux客户操作系统同时受益。
Optimizations to these Linux components (such as the new o (1) scheduler in the 2.6 kernel) benefit both the hypervisor (the host operating system) and the Linux guest operating systems.
这里设置调度程序的方法将导致在其中一个线程停止时整个调度程序停止。
The way the scheduler is set up here causes the whole scheduler to stop when one thread does so.
这样的示例有调度驱动程序所使用的传递记录应用程序，来自现场销售代表的订单输入系统等。
Examples of this are the delivery recording applications used by dispatch drivers, order entry systems from field sales representatives, and so on.
前面的SHEEP应用程序例子说明了使用时间触发预定行为的弱点——这个程序可以跳过调度触发。
The earlier SHEEP application example illustrated a weakness in using time to trigger scheduled actions — the program can skip over schedule triggers.
在每个服务器上，调度程序将启动爬网程序，并且将对集合进行更新以使其具有相同的内容。
On each server, the scheduler will start the crawlers, and the collections will be updated to have the same content.
然后，每个应用程序服务器都将使用自己的调度程序线程在其内执行自己的分派。
Each application server would then perform its own dispatching within itself, using its own dispatcher thread.
它使用一个调度程序来发起周期性的事件，比如爬网程序执行和全文索引维护。
It USES a scheduler to initiate periodic events, such as crawler executions and full-text index maintenance.
由于可能同时调度多个并发的XMLHTTP请求，应用程序本质上变成了一个并发程序，而并发很难实现。
Because multiple concurrent XML HTTP requests can be scheduled in parallel, our application essentially becomes a concurrent program — and concurrency is hard.
随着调度程序数的增长，一个调度程序将消息“丢失到”某些其他调度程序的可能性也在增加，而且(至少在理论上)这个问题可能愈演愈烈。
As the number of dispatchers increases, the probability of one dispatcher "losing" the message to some other dispatcher also increases, and (in theory, at least) this problem becomes exacerbated.
其次，字节码调度程序只是一个简单地从内存中直接读取，转而间接调度分支程序的过程。
Second, a bytecode dispatch is a single direct memory read, followed by a single indirect branch.
调度逻辑直接将业务对象发布到所有与更改相关的应用程序(在本例中只有一个应用程序)。
The dispatching logic simply publishes business objects to all applications interested in the change (in this case, only one application).
这个示例使用 “at”调度程序在特定的日期和时间向假脱机程序提交作业。
This example uses the "at" scheduler to submit a job to the spooler at a specific date and time.
应用程序在设计上可拥有多个用户级线程，并将它们计划为由应用程序或libpthread中的pthread调度程序处理。
Applications can be designed to have user-level threads that are scheduled to work by the application or by the pthreads scheduler in libpthreads.
当然，前面使用at调度程序的技术也可以改为使用 cron 调度程序。
The same technique shown previously using the at scheduler can of course be used with the cron scheduler as well.
包含Pausable throws 字句的方法在运行时由一个调度程序处理，该调度程序包含在 Kilim库中。
Methods containing the Pausable throws clause are processed at runtime by a scheduler, which is part of the Kilim library.
如前所述，PortalSearch包括用来启动爬网程序和索引维护处理的调度程序，其中索引维护处理可以删除过时的文档和断开的链接。
As described above, Portal Search includes a scheduler to start the crawlers and the index maintenance process that removes outdated documents and broken links.
由于标准Linux内核就是一个系统管理程序，因此它会从对标准内核的修改中获益良多(内存支持、调度程序等)。
Because the standard Linux kernel is the hypervisor, it benefits from the changes to the standard kernel (memory support, scheduler, and so on).
调度程序允许一个团队为各程序和一些具有所需技能的成员只获取事例。
The scheduler allows a team to get instances only for apps for which some team member has the required skill.
本程序采用的仿真策略是事件调度法，故主要的工作就是围绕着事件表进行并处理相应的子程序。
The simulation strategy that this procedure adopts is the event scheduling. Therefore, the main work focuses on dealing with the event table and processing the corresponding subprograms.
例如，当通过启动. EXE文件启动一个程序时，系统调度器就为该程序创建一个新的进程。
When you start a program by launching an EXE, for example, the system scheduler creates a new process for that program.
提出了一种能自动对内存的TSR程序进行检测、释放，而管理程序本身不占用任何内存的调度管理方法。
A schedule which does not use any memory is given to detect and release the TSR in memory automatically.
表示处于禁用状态的调度程序，并提供重新启用调度程序处理的方法。
Represents the dispatcher when it is in a disable state and provides a means to re-enable dispatcher processing.
表示处于禁用状态的调度程序，并提供重新启用调度程序处理的方法。
Represents the dispatcher when it is in a disable state and provides a means to re-enable dispatcher processing.
应用推荐