Remove unused crates from the project

[garypen]

Remove some unused crates and convert our redis tests to use the fred crate. That means we can remove our dev dependency on the redis crate.

This yielded a 1.5% reduction in test build time on my laptop.

Note: This is an exploratory PR, since it's fairly tricky to get unused crates information across multiple platforms with various conditional compilations in play.

---

Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

• Changes are compatible¹
• Documentation² completed
• Performance impact assessed and acceptable
• Tests added and passing³
  • Unit Tests
  • Integration Tests
  • Manual Tests

Exceptions

Note any exceptions here

Notes

Footnotes

1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩

2. Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩

3. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩

[github-actions]

@garypen, please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

[router-perf]

CI performance tests

• events_big_cap_high_rate - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity
• events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• events - Stress test for events with a lot of users and deduplication ENABLED
• large-request - Stress test with a 1 MB request payload
• step - Basic stress test that steps up the number of users over time
• xlarge-request - Stress test with 10 MB request payload
• reload - Reload test over a long period of time at a constant rate of users
• no-graphos - Basic stress test, no GraphOS.
• xxlarge-request - Stress test with 100 MB request payload
• step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• const - Basic stress test that runs with a constant number of users

[SimonSapin]

I don’t find the lint in the diff. Is it meant to be a new file?

[garypen]

I don’t find the lint in the diff. Is it meant to be a new file?

fd4b54b

[Geal]

the goal of using a different client was to make sure that there's nothing specific to fred that would mess with the data, but we can remove it yes

[garypen]

the goal of using a different client was to make sure that there's nothing specific to fred that would mess with the data, but we can remove it yes

I did wonder about that, but concluded that we should be testing fred since it's our primary (in fact, only) client in the router. We could add back the old test if it's useful.