Currently the way the DB is structured there isn't anyway to denote "this hardware was tested with these settings used on a benchmark", you can only say which benchmark was used. This is fine on a small scale with the user needing to track settings used externally, but there should be a way to do this in the app so it's all consolidated and ideally populates the charts/graphs with relevant info like resolution, graphics preset, chunk size, etc.
Ideally, we'd have tests link to an intermediary "BenchmarkSettings" object which contains a list of settings used in the test and links back to the Benchmark object so we can make an easy search like "search for tests using this benchmark, any settings"
Currently the way the DB is structured there isn't anyway to denote "this hardware was tested with these settings used on a benchmark", you can only say which benchmark was used. This is fine on a small scale with the user needing to track settings used externally, but there should be a way to do this in the app so it's all consolidated and ideally populates the charts/graphs with relevant info like resolution, graphics preset, chunk size, etc.
Ideally, we'd have tests link to an intermediary "BenchmarkSettings" object which contains a list of settings used in the test and links back to the Benchmark object so we can make an easy search like "search for tests using this benchmark, any settings"
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the way the DB is structured there isn't anyway to denote "this hardware was tested with these settings used on a benchmark", you can only say which benchmark was used. This is fine on a small scale with the user needing to track settings used externally, but there should be a way to do this in the app so it's all consolidated and ideally populates the charts/graphs with relevant info like resolution, graphics preset, chunk size, etc.
Ideally, we'd have tests link to an intermediary "BenchmarkSettings" object which contains a list of settings used in the test and links back to the Benchmark object so we can make an easy search like "search for tests using this benchmark, any settings"