Re: get_tags_in_range vs get_tags_in_window

[Marcus Müller]

Hello Jason,

no, there's no benefit. `get_tags_in_window` just calls `get_tags_in_range`; citing: 
gnuradio/gnuradio-runtime/lib/block.cc:

void block::get_tags_in_window(std::vector<tag_t>& v,
                               unsigned int which_input,
                               uint64_t start,
                               uint64_t end)
{
    d_detail->get_tags_in_range(v,
                                which_input,
                                nitems_read(which_input) + start,
                                nitems_read(which_input) + end,
                                unique_id());
}

So, sadly, no reduction of computational load (by the way, to evaluate computational load 
of the tagging system, we used to use `perf top -a` a lot).

Best regards,
Marcus

On 19.04.23 15:59, Jason Matusiak wrote:
> I have a block that is making heavy use of tags: reading, reacting, and adding in new 
> tags.  It seems like this block might be a little costly processor resource wise.  I am 
> currently using get_tags_in_range, so I was wondering if there was a cost benefit to go 
> with get_tags_in_window instead?
>
> If it matters, this is a general_work block where I am taking in X samples, stuffing in 
> random samples if there were any drops detected (to make up for them), and outputting Y 
> samples.  The block isn't that complicated, but there is significant tag manipulation, and 
> I think that that is costing me some.