轮询多个线程和 CPU 使用情况

发布于 2024-11-30 19:26:29 字数 307 浏览 3 评论 0原文

我有一个调用，该调用接收来自用户的作业列表，说用户发布了 3 个作业 A、B 和 C，它们都开始在自己的线程 AT、BT 和 CT 中执行，然后我开始监视这 3 个线程，如果其中一个线程作业失败表示 B 失败，我需要向 A 和 C 发出信号停止。当所有线程停止返回时，全部成功时为 true，如果其中一个失败为 false。

目前我有一个很大的 while 循环，可以进行检查并休眠 50 毫秒，这可以工作，但我想知道是否有更好的方法可以在不进行任何休眠的情况下执行此操作，我尝试休眠 0 毫秒 AFAIK，这使我的线程结束cpu que，但它仍然使用了太多的 cpu 大约 60%。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

甜宝宝 2024-12-07 19:26:29

这听起来像是的用例ExecutorCompletionService

// wrap tasks A, B and C into runnables (or callables if you need some result):
Callable<Result> taskA = ...;
Callable<Result> taskB = ...;
Callable<Result> taskC = ...;

// create an ExecutorCompletionService
// to which you must pass an ExecutorService
// (choose one according to your precise use case)
// (the newCachedThreadPoolExecutor might not be a sensible choice)
ExecutorCompletionService e = new ExecutorCompletionService(Executors.newCachedThreadPoolExecutor());

Set<Future<Result>> futures = new HashSet<>();

// submit your tasks:
futures.add(e.submit(taskA));
futures.add(e.submit(taskB));
futures.add(e.submit(taskC));

// now call take() on the executor completion service,
// which will block the calling thread until the first task has completed
// either succesfully or abruptly (with an exception)
Future<Result> f = e.take();

此后，当您调用 f.get() 时，您将获得 Result 的实例，否则将抛出异常一个ExecutionException（包装执行抛出的异常）。任何一种都会立即发生（感谢执行器完成服务）。

然后你会做出相应的反应：如果f.get()抛出异常，从futures集合中删除f，迭代集合（即通过您提交的其他任务），以及 .cancel() 它们。 Callable 必须被编码为可取消的，否则对 .cancel() 的调用将不会执行任何操作。

This sounds like a use case for ExecutorCompletionService

// wrap tasks A, B and C into runnables (or callables if you need some result):
Callable<Result> taskA = ...;
Callable<Result> taskB = ...;
Callable<Result> taskC = ...;

// create an ExecutorCompletionService
// to which you must pass an ExecutorService
// (choose one according to your precise use case)
// (the newCachedThreadPoolExecutor might not be a sensible choice)
ExecutorCompletionService e = new ExecutorCompletionService(Executors.newCachedThreadPoolExecutor());

Set<Future<Result>> futures = new HashSet<>();

// submit your tasks:
futures.add(e.submit(taskA));
futures.add(e.submit(taskB));
futures.add(e.submit(taskC));

// now call take() on the executor completion service,
// which will block the calling thread until the first task has completed
// either succesfully or abruptly (with an exception)
Future<Result> f = e.take();

After this, when you call f.get(), you will either get an instance of Result or it will throw an ExectutionException (wrapping the exception thrown by the execution). Either one will happen immediately (thanks to the executor completion service).

Then you will react accordingly: if f.get() throws an exception, remove f from the futures set, iterate through the other elements of the set (that is, through the other tasks you submitted), and .cancel() them. The Callables must be coded to be cancelable, otherwise the call to .cancel() will do nothing.

回复收藏 0 原文