当前位置：文江博客话题详情

线程占用大量CPU

发布于 2024-10-20 21:26:17 字数 257 浏览 2 评论 0原文

我正在使用 Thread 来帮助在 perl 中执行线程；我想说我对线程相当陌生。

我的程序中有一个名为“最大线程”的变量。如果线程数量低于这个数字，就会提示新的线程。我使用 while 循环将当前现有线程数与最大线程变量进行比较。

我假设 while 循环是消耗我的 cpu 的东西。

无论如何，我可以让“老板”或“经理”线程（核心线程）在安排和管理线程时不占用那么多的CPU吗？如果我的 CPU 仅仅因为管理器线程而提高，那么线程根本没有任何意义！

原文

分享到QQ

分享到微博

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

发布评论

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

天赋异禀 2024-10-27 21:26:18

如果您想保留当前模型，则应该有某种信号（可能是信号量），当工作人员太多时，线程启动器可以阻止该信号。

一个更简单的模型是拥有一个工作人员池，并通过 Thread::Queue 为他们提供工作。

my $q = Thread::Queue->new();

my @workers;
for (1..$MAX_WORKERS) {
    push @workers, async {
       while (my $job = $q->dequeue()) {
           ...
       }
    };
}

for (...) {
    $q->enqueue(...);
}

# Time to exit
$q->enqueue(undef) for 0..$#workers;

# Wait for workers to finish.
$_->join() for @workers;

If you want to keep the current model, you should have some kind of signal (probably a semaphore) on which the thread launcher can block when there are too many workers.

A much simpler model is to have a pool of workers, and given them work via a Thread::Queue.

my $q = Thread::Queue->new();

my @workers;
for (1..$MAX_WORKERS) {
    push @workers, async {
       while (my $job = $q->dequeue()) {
           ...
       }
    };
}

for (...) {
    $q->enqueue(...);
}

# Time to exit
$q->enqueue(undef) for 0..$#workers;

# Wait for workers to finish.
$_->join() for @workers;

回复收藏 0 原文

话少情深 2024-10-27 21:26:18

我不使用 Perl，但从一般异步编程的角度来看，您需要一个不会阻塞主线程的线程池管理器，并且这可以通过多种方式完成。一方面，您可以专用一个线程（耶！）来执行类似以下操作（伪代码）：

while program not terminating:
   wait a quarter-second or so, then
      do your "are-there-enough-threads" check

操作系统或抽象的运行时库通常会提供某种等待函数，该函数会暂停线程，直到达到特定数量为止。时间已经过去（因此在此期间不占用调度程序资源）。

或者，如果您的程序是事件驱动的（如在 GUI 环境中），您可以通过发布计时器消息来在主线程之外执行类似的池管理，这是操作系统通常提供的另一项服务。

I don't use Perl, but speaking from a general asynchronous programming perspective, you want a thread pool manager that isn't clogging up the main thread, and this can be accomplished multiple ways. For one thing, you can dedicate a thread (yay!) to doing something like this (pseudocode):

while program not terminating:
   wait a quarter-second or so, then
      do your "are-there-enough-threads" check

The OS, or your abstracted run-time library, will generally supply some kind of wait function that halts the thread until a specific amount of time has passed (thus taking up no scheduler resource during that time).

Alternatively, if your program is event-driven (as in a GUI environment), you could do similar pool management off the main thread by posting yourself timer messages, which is another service generally supplied by the OS.

回复收藏 0 原文