torrust-tracker
torrust-tracker copied to clipboard
Add DashMap implementation for torrent repository and set as used one
DashMap does not support ordering of keys that we use right now for our scrape responses, since DashMap works using multiple inner HashMaps (sharded).
When I implement the torrent repository limit, I plan on adding a new HashMap that keeps track of the storage priority of torrents. We could also use the ordering of that HashMap for our torrents and scrape responses.
I will include https://github.com/torrust/torrust-tracker/issues/567 as a part of this PR as well to fix any related failing tests. Especially for the ordering of torrents in the API response.
I guess this was superseded by https://github.com/torrust/torrust-tracker/pull/645, right @mickvandijke?