valence/performance_tests/players/Cargo.toml

[package]
name = "players"
version = "0.1.0"
edition = "2021"

[dependencies]
tracing-subscriber = "0.3.16"
valence = { path = "../.." }
Add performance tests (#113) Adds the performance_tests/ directory. In the future we could use our own fake client software instead of rust-mc-bot. This would make it easier to run the tests. 2022-10-15 15:18:03 +11:00			`[package]`
			`name = "players"`
			`version = "0.1.0"`
			`edition = "2021"`

			`[dependencies]`
Replace `log` crate with `tracing` (#157) The `tracing` crate seems to be the go-to logging/profiling/instrumentation solution nowadays. Perhaps in the future we could use `tracing` for profiling instead of (or in addition to) the `perf`-based `cargo flamegraph` command. This would sidestep the issue of `rayon` polluting the output. I conducted an initial experiment by adding some more spans but wasn't very happy with the result. Log messages have also been improved. There is some additional context and events are raised when clients are added/removed from the server. 2022-11-17 13:22:44 +11:00			`tracing-subscriber = "0.3.16"`
Add performance tests (#113) Adds the performance_tests/ directory. In the future we could use our own fake client software instead of rust-mc-bot. This would make it easier to run the tests. 2022-10-15 15:18:03 +11:00			`valence = { path = "../.." }`
Replace `log` crate with `tracing` (#157) The `tracing` crate seems to be the go-to logging/profiling/instrumentation solution nowadays. Perhaps in the future we could use `tracing` for profiling instead of (or in addition to) the `perf`-based `cargo flamegraph` command. This would sidestep the issue of `rayon` polluting the output. I conducted an initial experiment by adding some more spans but wasn't very happy with the result. Log messages have also been improved. There is some additional context and events are raised when clients are added/removed from the server. 2022-11-17 13:22:44 +11:00