InternalRegistry vectors : order importance and efficiency

[younes-io]

ockam/implementations/rust/ockam/ockam_transport_tcp/src/registry/internal.rs

Line 11 in bc18114

pub(super) sender_workers: Vec<TcpSenderInfo>,

The InternalRegistry struct holds several vectors that track different types of entities, such as workers and processors, each associated with TCP connections.

I just want to know if order matters in these vectors ? Because if order doesn't matter, then maybe we could use other data structures like HashMap which might be more efficient, especially in frequent additions / removals /lookups..

[SanjoDeundiak]

Hey @younes-io , thanks for taking a look at this part of the code. The choice here is intentional. While the order doesn't matter and using HashMap is absolutely a good option too, I don't think it's certainly better, it's a trade-off. Vector may be more predictable, memory efficient and performant if the number of elements is relatively small (~up to 100). I don't think we would like to make a change without clear understanding of why it would be better

[SanjoDeundiak]

Don't hesitate to reopen the topic if you want