[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU
From: |
Johnathan Corgan |
Subject: |
Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU |
Date: |
Fri, 12 Dec 2008 07:49:24 -0800 |
On Thu, Dec 11, 2008 at 1:46 PM, Marcus D. Leech <address@hidden> wrote:
> Also, I looked into the process details of the process running
> usrp_ra_receiver.py, and found that it had
> 25 threads. That must mean that each block runs in its own thread
> now?
Yes. The "thread-per-block" design by Eric allows, in many cases, for
the flowgraph throughput to rise until an individual block consumes
100% of a single core. This is a great improvement over the
single-threaded scheduler that would rate-limit when an entire
flowgraph of blocks consumed a single core.
You can switch between the two for comparison:
$ export GR_SCHEDULER=STS # single-threaded-scheduler (old)
$ export GR_SCHEDULER=TPB # thread-per-block (new, default)
-Johnathan
- [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Marcus D. Leech, 2008/12/10
- RE: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Bob McGwier, 2008/12/10
- Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Marcus D. Leech, 2008/12/10
- Message not available
- Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Marcus D. Leech, 2008/12/12
- Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Johnathan Corgan, 2008/12/15
- Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Jing Cao, 2008/12/27
- Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU, Johnathan Corgan, 2008/12/28