No, it's just a warning. You probably aren't going to cause any problems by turning the priority of a process up or down a notch. And there won't be any irreversible damage; anything you do mess up can be fixed by a restart. Just make sure to save your work first before experimenting!
There are a couple of common things that can go wrong (and thus that you should watch out for):
You can crank up the priority of a non-system process so high that it can cause the system to become unstable and non-responsive because the system processes don't get enough time.
You can crank down the priority of a system process so low that it doesn't get enough time, causing your system to become unstable and non-responsive. (Although I think they've fixed some of this more recently by preventing you from altering the priority of certain so-called "critical" system processes.)
In my experience, assuming a decently fast and stable machine, as long as you stay away from the "Real Time" option, you will be fine. Turning non-system process down in priority level is even less likely to cause harm.
If the process you're adjusting interacts with another process, you could potentially create a priority inversion, which is one way to get a deadlock (i.e., it could cause the process or the one it's interacting with to hang).
But if it's just a standalone program that's busy computing, dropping its priority a notch is not likely to cause any problems.
The stability problems mentioned in the warning are an issue only if you change the priority relative to dependent system processes.
发布评论
评论（2）
不，这只是一个警告。将进程的优先级调高或调低可能不会造成任何问题。并且不会造成任何不可挽回的损害；你做的任何事情都可以通过重新启动来解决。请确保在实验之前先保存您的工作！
有一些常见的事情可能会出错（因此您应该注意）：
您可以提高非系统进程的优先级 > 太高，可能会导致系统变得不稳定且无响应，因为系统进程没有足够的时间。
您可以降低系统进程的优先级，使其没有足够的时间，从而导致系统变得不稳定且无响应。 （尽管我认为他们最近通过阻止您更改某些所谓的“关键”系统进程的优先级来修复了其中的一些问题。）
根据我的经验，假设一台速度相当快且稳定的机器，只要您远离“实时”选项，您将没事。降低非系统进程的优先级更不可能造成损害。
No, it's just a warning. You probably aren't going to cause any problems by turning the priority of a process up or down a notch. And there won't be any irreversible damage; anything you do mess up can be fixed by a restart. Just make sure to save your work first before experimenting!
There are a couple of common things that can go wrong (and thus that you should watch out for):
You can crank up the priority of a non-system process so high that it can cause the system to become unstable and non-responsive because the system processes don't get enough time.
You can crank down the priority of a system process so low that it doesn't get enough time, causing your system to become unstable and non-responsive. (Although I think they've fixed some of this more recently by preventing you from altering the priority of certain so-called "critical" system processes.)
In my experience, assuming a decently fast and stable machine, as long as you stay away from the "Real Time" option, you will be fine. Turning non-system process down in priority level is even less likely to cause harm.
如果您正在调整的进程与另一个进程交互，您可能会创建一个优先级反转，是导致死锁的一种方法（即，它可能导致进程或与之交互的进程挂起）。
但如果它只是一个忙于计算的独立程序，那么将其优先级降低一个档次不太可能会导致任何问题。
仅当您更改相对于依赖系统进程的优先级时，警告中提到的稳定性问题才会出现问题。
If the process you're adjusting interacts with another process, you could potentially create a priority inversion, which is one way to get a deadlock (i.e., it could cause the process or the one it's interacting with to hang).
But if it's just a standalone program that's busy computing, dropping its priority a notch is not likely to cause any problems.
The stability problems mentioned in the warning are an issue only if you change the priority relative to dependent system processes.