Hi Booth, the throttle block is an "average rate" limiter, not a measurement block - it simply pauses copying the input to the output if your sample generation is faster on long-term average than set in the throttle rate.
So, if you set a throttle rate that is higher than what your PC can do, the Throttle will just not pause and copy in- to output. It does nothing. (Ok, it wastes CPU time and memory bandwidth...). What you want is the "probe rate" block connected to a "message debug" block, for an easy assessment. PS: Don't subscribe using Nabble (this is not a forum, but an email list), but simlpy directly via https://lists.gnu.org/mailman/listinfo/discuss-gnuradio using your email address. It works much better and is easier to use. Nabble tends to not correctly represent discussions. Best regards, Marcus On 25.04.2017 12:18, Booth wrote: > Dear all, > I wondered what would be the maximum sample rate that my PC can handle for > a basic psk mod-demod. I have used the “prbs_test.grc” from gr-mapper as it > contains all the necessary blocks. I changed the sample rate for the > throttle to 32k, 320k,10M, 100M even 10G but the system did not break down. > I repeated the experiment using different examples but the result was the > same. > What went wrong and do you know any appropriate projects for speed > measurements. > > > > -- > View this message in context: > http://gnuradio.4.n7.nabble.com/Speed-test-went-wrong-tp63632.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > _______________________________________________ > 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
