Remove overcomplicated iterator

[IvanPleshkov]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you lint your code locally using cargo fmt command prior to submission?
3. Have you checked your code using cargo clippy command?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

[generall]

In theory the amount of edges for a single node could be larger than get_m - in case we are creating additional links based in indexed payload. In this case we need to limit scoring to only the first M points which pass the filter, even if there are more than M point in total

[generall]

Benchmarks comparision https://docs.google.com/spreadsheets/d/1QQgZMFpV3fbVNxXJoz3tZGQSyR7eX-q4eAg8l4BPGr0/edit?usp=sharing

[monatis]

Is the row 5 an outlier for the fixing trick? Anyway, it seems to be offering 15-to-20% speedup compared to the master.

Yes, already tired of the holiday, returning back with full energy on Monday 😄

[IvanPleshkov]

measurement latest commit with master:
https://docs.google.com/spreadsheets/d/1v07WhdGxh0XwRAg7NY4is1WZQI1dZqNHnjzDFqUrgBM/edit?usp=sharing

[agourlay]

I was wondering why you got a new weird clippy error then I found this line

stable-x86_64-unknown-linux-gnu updated - rustc 1.60.0 (7737e0b5c 2022-04-04) (from rustc 1.59.0 (9d1b2106e 2022-02-23))

Looks like we are pulling the new release right away, it might make sense to lock the rust version used in the CI pipeline.

[generall]

suggested a small refactoring #450 (benchmarks are not affected)

[generall]

Also profile results