您要查找的是不是：
- The connection concentrator is associated with context switching of agents. 连接集中器与代理的上下文切换相关联。
- The CPU simply becomes overburdened by context switching between threads. 由于要在线程间进行上下文切换,因此CPU简直变成了超载。
- TSS holds hardware context information for each CPU which helps to take effect in context switching. TSS中保存了每个CPU的硬件上下文信息,它有助于有效地切换上下文。
- This is most likely due to the cost of context switching between so many threads. 这最有可能是由于在这么多的线程间切换上下文的开销而导致的。
- This is true if there is no context switching or if the impersonation is at the server level. 没有上下文切换或在服务器级进行模拟时,将出现这种情况。
- Note that context switching on the front-end server does not grow significantly as processor usage increases. 请注意,当处理器的使用增加时,前端服务器的上下文切换不会显著增长。
- Rather, all protothreads run on the same stack and context switching is done by stack rewinding. 而且，所有的实例运行在同样的堆栈和内容切换通过堆栈反转完成。
- The following figure shows how context switching begins to level off on a two-processor front-end server as processor usage increases. 下图显示了双处理器前端服务器的上下文切换是如何随着处理器使用的增加而渐趋平稳的。
- The topics in this section provide information to help you understand and implement context switching in modules and sessions. 本节中的主题提供信息来帮助您了解和实现在模块和会话中切换上下文。
- Number of scheduler context switches that this task has completed. 此任务完成的计划程序上下文切换数。
- The duration of the context switch is limited to the scope of the query being executed. 时,上下文切换的持续时间限制为执行查询的范围。
- If SESSION_USER is called after a context switch, SESSION_USER will return the user name of the impersonated context. 如果在切换上下文之后调用SESSION_USER,SESSION_USER将返回模拟上下文的用户名。
- Specifies that the context switch cannot be reverted back to the previous context. 指定上下文切换不能恢复到以前的上下文。
- Thread Stack, each thread has a dedicated stack for its own execution and context switch. 线程堆栈，每个线程都有自己执行与上下文切换的专用堆栈。
- While the context switch to the database user is active, any attempt to access resources outside of the database will cause the statement to fail. 当到数据库用户的上下文切换处于活动状态时,任何对数据库以外资源的访问尝试都将导致语句失败。
- While the context switch to the database user is active, any attempt to access resources outside the database will cause the statement to fail. 当到数据库用户的上下文切换处于活动状态时,任何对数据库外部资源的访问尝试都会导致语句失败。
- This means that after the context switch, any resource within the server that the impersonated login has permissions on can be accessed. 这意味着上下文切换后,可以访问模拟的登录帐户在服务器内具有权限的任何资源。
- A context switch involves saving the context of the running task and restoring the divviously-saved context of the other. 上下文切换包括保存正在运行的任务的上下文和恢复早先保存的另一个任务的上下文。
- I've seen way too much code that avoids data copies by doing something even worse, like forcing a context switch or breaking up a large I/O request. 我看到过太多的代码为了避免数据拷贝，最后的结果是比拷贝数据更糟糕，比如环境切换或者分解一个大的I/O请求。
- The advantages to this is that if a thread is about to give up a mutex, you don't have to context switch to another thread. 这样做的优点是当一个线程要放弃一个互斥锁的时候，你不需要上下文切换到另外的线程中去。
