Are you looking at the full 24-hour interval, or are you looking at prime shift interval?
您是否查看了全天24小时的间隔，或是否查看了主要班次间隔？
Have you actually disabled half of your cluster during peak prime shift to validate that the workload still fits?
您是否在峰值转换期间真正禁用了集群的一半，以验证仍然可以承受工作负载？
Shift interval: All values plotted that fit within prime shift, which is defined as Monday through Friday 8 AM to 4 PM
班次间隔：在主要班次内划分的所有值，定义为星期一至星期五的上午 8 点到下午 4 点。
For example, in the lower middle portion of figure 9 you can see that the Compact task (turquoise line) was running during prime shift.
例如，在图9的下半部分中，可以看到Compact任务(蓝绿色)正在主要班次期间运行。
While this is a single occurrence in this sample, for sizing purposes, you should determine how often these tasks run during prime shift.
虽然在这个示例中只出现了一次，但为了分级目的，您应该确定这些任务在主要班次期间的运行频率。
Running AdminP during prime shift can be somewhat like running agents in that you never know exactly how many resources your AdminP updates require.
在主要班次期间运行adminp有点像运行代理，因为您永远也不知道AdminP更新到底需要多少资源。
By changing this to a daily prime-shift view (see figure 6), you can easily see what your transactions rates were during prime shift over the same period.
通过将其更改为每日主要班次视图(参见图6)，可以容易地看到在同一期间内主要班次期间的事务处理率。
In addition, exercise care when you run Compact, Updall, Fixup, or other maintenance tasks during prime shift because there can be a large impact on your resources.
此外，在主要班次期间运行Compact、Updall、Fixup或其他维护任务时要多加小心，因为这可能对资源产生极大影响。
For this article, we will look at the performance of these DPARs during "prime shift." (prime shift is defined as Monday through Friday, from 8 AM to 4 PM in the local time of the DPARs.)
对于本文，我们将考察主要工作时间(prime shift)这些DPAR的性能(主要工作时间定义为周一到周五，DPAR的本地时间上午8点到下午4点)。
For this article, we will look at the performance of these DPARs during "prime shift." (prime shift is defined as Monday through Friday, from 8 AM to 4 PM in the local time of the DPARs.)
对于本文，我们将考察主要工作时间(prime shift)这些DPAR的性能(主要工作时间定义为周一到周五，DPAR的本地时间上午8点到下午4点)。
应用推荐