Hi Ihab -

I recommend checking out this paper on performance counters & ctrlport. The
dependency on `thrift` can be a bit painful, but these are great tools in
GNU Radio for instrumenting your application and optimizing performance.

http://conferences.sigcomm.org/sigcomm/2013/papers/srif/p65.pdf

Cheers,
Ben

On Mon, Aug 29, 2016 at 12:38 PM, Dave NotTelling <[email protected]>
wrote:

> One way I check for bottlenecks it to run 'top -H' and watch the various
> threads.  If you see any one thread pegged at 100% then it needs to be
> optimized.  At least that's my method :)
>
> On Mon, Aug 29, 2016 at 9:46 AM, Ihab Zine <[email protected]> wrote:
>
>> Hi Marcus,
>>
>> I have been through the GNU RADIO tutorials , I also dived into adapting
>> gr-dvbt, and it worked for me. But how can i find out where my transceiver
>> BER bottlenecks and where my computational bottlenecks come from? Is the a
>> method or steps i can follow? I need some hints on this.
>>
>> Best Regards
>> Ihab
>>
>> On 24 August 2016 at 15:12, Ihab Zine <[email protected]> wrote:
>>
>>> Hi Ron and Marcus,
>>>
>>> For frequency higher than 6 Ghz,  a down converter can be used to over
>>> come this problem.
>>>
>>> for the data rate and bandwidth, the PC i'm using has the following
>>> specifications:
>>>
>>> Architecture:              x86_64
>>> CPU op-mode(s):      32-bit, 64-bit
>>> Byte Order:                Little Endian
>>> CPU(s):                      20
>>> On-line CPU(s) list:    0-19
>>> Thread(s) per core:    2
>>> Core(s) per socket:    10
>>> Socket(s):                  1
>>> NUMA node(s):         1
>>> Vendor ID:                 GenuineIntel
>>> CPU family:               6
>>> Model:                       63
>>> Model name:             Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
>>> Stepping:                  2
>>> CPU MHz:                1553.804
>>> CPU max MHz:         3300.0000
>>> CPU min MHz:          1200.0000
>>> BogoMIPS:                5197.32
>>> Virtualization:            VT-x
>>> L1d cache:                32K
>>> L1i cache:                 32K
>>> L2 cache:                 256K
>>> L3 cache:                 25600K
>>> NUMA node0 CPU(s):     0-19
>>>
>>> I think it can handle this rate. Please correct me if i'm Wrong.
>>>
>>> i have other questions:
>>>
>>>
>>>    - There are (synchronizers, equalizers, channel codes etc) blocks in
>>>    the gr-dvbt project why I cant use them?
>>>    - when you mentioned channel coding do you mean that i need to
>>>    create a new one? and Why would I need it?
>>>    - If i need BCH performance Why is difficult to achieve?
>>>    - if the data requirement is fine (CPU and etc), what is the best
>>>    way to start building the receiver? How can I figure out the blocks That 
>>> i
>>>    need for this receiver?
>>>
>>>
>>> Regards
>>> Ihab
>>>
>>>
>>> On 23 August 2016 at 14:34, Ihab Zine <[email protected]> wrote:
>>>
>>>> Hi Ron,
>>>>
>>>> 1) Frequency range: 1.5 - 38 GHz
>>>>
>>>> 2) Bandwidth range : 2 - 56 MHz
>>>>
>>>> 3) Modulation : Qpsk - 256 QAM
>>>>
>>>> 4) Data rate range : 150Mbit/s - 326Mbit/s.
>>>>
>>>> 5) Error correction method : i thinks it is FEC.
>>>>
>>>> Ihab
>>>>
>>>> On 22 August 2016 at 12:33, Ihab Zine <[email protected]> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I'm working on a project using GnuRadio And USRP 205 mini, i'm at the
>>>>> stage where i need to demodulate a microwave link signal.
>>>>>
>>>>> Anyone has an experience with Microwave link or tried to do something 
>>>>> similar?
>>>>> Is it possiable to do it in gnuradio? or is there another approaches to do
>>>>> it?
>>>>>
>>>>> I'd appreciate any information you could give me.
>>>>>
>>>>> Thanks
>>>>> Ihab
>>>>>
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> [email protected]
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to