You can configure to activate any profile automatically at appointed time with a built-in scheduler.
你可以配置为在指定时间自动启动任何一台内置的调度。
Trickle messages are conveyed in scheduler RPC messages, so they may not be delivered immediately after being generated.
触发消息通过调度服务的远端过程调用(rpc)消息进行传递，因此它们可能不会在消息生成后立即就被发送。
The advantage of doing this is to override the system's built-in scheduler to force a process to run only on specified CPUs.
这样做的好处是可以覆盖系统内建调度器，迫使一个进程只在指定的 CPU 上运行。
Trickle messages are asynchronous and reliable. Trickle messages are conveyed in scheduler RPC messages, so they may not be delivered immediately after being generated.
触发消息是异步和可靠的。触发消息通过调度服务的远端过程调用(rpc)消息进行传递，因此它们可能不会在消息生成后立即就被发送。
In the simple examples, all threads get equal attention from the scheduler.
在简单的示例中，所有线程都获得调度程序同等的关注。
The part of the kernel called the scheduler swaps jobs in and out so that they all get a turn.
内核中称为调度程序的部分将工作换进换出，从而让所有工作都获得一轮执行。
This new scheduler can operate in bounded time regardless of the number of tasks to execute.
不管需要运行的任务有多少个，新的调度程序都会在有限的时间内运行。
In the 2.4 scheduler, the timeslice recalculation algorithm requires that all processes exhaust their timeslice before their new timeslices can be recomputed.
在2.4版本的调度器中，时间片重算算法要求在所有的进程都用尽它们的时间片以后，它们的新时间片才会被重新计算。
Scheduler nodes -- In order to run a workload on the cluster, users should submit their work to a scheduler node.
调度器节点 ——为了在集群上运行工作负荷，用户应当把自己的工作提交到调度器节点。
This means that once a scheduler is validated in user space, it's quite simple then to migrate this scheduler into the kernel for use.
这意味着一旦在用户空间中验证了调度器，将此调度器迁移到内核以供使用会非常简单。
For example, you could implement these ideas in traditional embedded systems in place of a traditional scheduler for work scheduling.
例如，可以将这些理念应用到传统的嵌入式系统当中，取代原有的调度程序来进行任务调度。
His motivation in working on the new scheduler was to create a completely o (1) scheduler for wakeup, context-switch, and timer interrupt overhead.
他编写这个新调度器的动机是为唤醒、上下文切换和定时器中断开销建立一个完全o(1)的调度器。
In this case, the scheduler on the DB2 UDB server needs to connect to the tools catalog database in order to retrieve any required information about the tasks to be run.
在这种情况下，DB 2UDB服务器上的调度程序需要连接到工具目录数据库，以便检索运行任务需要的信息。
It was called the o (1) scheduler, because it operated in constant time, regardless of the number of tasks to schedule.
这被称为O(1)调度器，因为其在固定时间内工作，而无论要调度的任务数量。
In short, the scheduler wasn't complex but was simple and fast.
简而言之，该调度器并不复杂但是简单快捷。
In this type of scheduler, the time it takes to schedule a task is a function of the number of tasks in the system.
在这种调度器中，调度任务所花费的时间是一个系统中任务个数的函数。
The new O(1) scheduler in the 2.6 kernel is a great benefit to performance, even when a large number of tasks exists.
内核中新的O(1)调度程序对性能有很大的提升，即使存在很多任务的情况下也是如此。
You have now seen how the scheduled destruction of a WS-Resource can be implemented using the scheduler service in WebSphere Application Server, Enterprise Edition.
现在您已经看到了可以如何使用WebSphereApplicationServerEnterpriseEdition中的调度程序服务来实现Web服务资源的预定销毁。
LinSched is a Linux scheduler simulator that resides in user space.
LinSched是驻留在用户空间中的Linux调度器模拟器。
Applications can be designed to have user-level threads that are scheduled to work by the application or by the pthreads scheduler in libpthreads.
应用程序在设计上可拥有多个用户级线程，并将它们计划为由应用程序或libpthread中的pthread调度程序处理。
In addition to the scheduler on the host servers, the snippet processors have their own smart preemptive scheduler that allows snippets from multiple queries to execute simultaneously.
除了主机服务器上的调度器外，snippet处理器也具有自己的智能抢占式调度器，允许同时执行来自多个查询的snippet。
From this short article, you can see the value in simulating the Linux scheduler in user space.
从这篇简短的文章，您可以看到用户空间中模拟Linux调度器的价值。
The source for the 2.6 scheduler is well encapsulated in the file /usr/src/linux/kernel/sched.c.
版本调度器的源代码都很好地封装到了 /usr/src/linux/kernel/sched.c 文件中。
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.
对这些Linux组件进行优化(例如2.6版本内核中的新o(1)调度程序)都可以让系统管理程序(主机操作系统)和Linux客户操作系统同时受益。
We strongly suggest that users be kept off the system unless they enter in through a controlled environment like a resource scheduler.
我们强烈建议把用户挡在系统之外，只允许他们通过受控的环境(比如资源调度程序)进入系统。
In local deployment, the collector and its invoking scheduler are deployed within the target JVM itself.
在本地部署中，收集器和它的调用调度程序部署在目标J VM中。
Although the thread scheduler, in principle, may switch threads in the middle and run them in different order, it tends not to.
虽然原则上线程调度程序可以在运行的中间切换线程并以不同的顺序运行它们，但是它往往不进行切换。
Finally, preemption wasn't possible in the earlier scheduler; this meant that a lower priority task could execute while a higher priority task waited for it to complete.
最后，在早期的内核中，抢占是不可能的；这意味着如果有一个低优先级的任务在执行，高优先级的任务只能等待它完成。
Use the backup scheduler included in the backup software.
使用备份软件里内含的备份规划器。
But the O (1) scheduler became unwieldy in the kernel.
但是O(1)调度器在内核中很笨拙。
应用推荐