add benchmark metadata for the dev profile

Author: lqd

site/build.rs

@@ -55,22 +55,11 @@ fn main() -> Result<(), Box<dyn Error>> {
         let manifest: toml::Value = toml::from_str(&manifest_contents)?;
 
         let table = manifest.as_table().unwrap();
-        let profile = table.get("profile");
-        let release = profile
-            .and_then(|p| p.as_table())
-            .and_then(|t| t.get("release"))
-            .and_then(|t| t.as_table());
-        let debug = release.and_then(|t| t.get("debug"));
-        let lto = release.and_then(|t| t.get("lto"));
-        let codegen_units = release.and_then(|t| t.get("codegen-units"));
-
+        let profiles = table.get("profile");
         let metadata = CompileBenchmarkMetadata {
             perf_config: config,
-            release_metadata: ProfileMetadata {
-                debug: debug.map(|v| v.to_string()),
-                lto: lto.map(|v| v.to_string()),
-                codegen_units: codegen_units.and_then(|v| v.as_integer().map(|v| v as u32)),
-            },
+            release_metadata: read_profile_metadata(profiles, "release"),
+            dev_metadata: read_profile_metadata(profiles, "dev"),
         };
         suite.insert(benchmark_name, metadata);
     }
@@ -82,3 +71,23 @@ fn main() -> Result<(), Box<dyn Error>> {
 
     Ok(())
 }
+
+/// If the manifest has `profile.*` entries, read some of the compilation metadata from a built-in
+/// profile with the given `profile` name, if it exists (for example, the options for cargo's
+/// optimized profile is named `release`).
+/// Note that some, or all, of the metadata that we want to display may be missing from the
+/// manifest: it just won't be shown in the UI in that case.
+fn read_profile_metadata(profiles: Option<&toml::Value>, profile: &str) -> ProfileMetadata {
+    let profile = profiles
+        .and_then(|p| p.as_table())
+        .and_then(|t| t.get(profile))
+        .and_then(|t| t.as_table());
+    let debug = profile.and_then(|t| t.get("debug"));
+    let lto = profile.and_then(|t| t.get("lto"));
+    let codegen_units = profile.and_then(|t| t.get("codegen-units"));
+    ProfileMetadata {
+        debug: debug.map(|v| v.to_string()),
+        lto: lto.map(|v| v.to_string()),
+        codegen_units: codegen_units.and_then(|v| v.as_integer().map(|v| v as u32)),
+    }
+}

site/src/benchmark_metadata/metadata.rs

@@ -22,6 +22,7 @@ pub struct ProfileMetadata {
 pub struct CompileBenchmarkMetadata {
     pub perf_config: serde_json::Value,
     pub release_metadata: ProfileMetadata,
+    pub dev_metadata: ProfileMetadata,
 }
 
 #[derive(serde::Serialize, serde::Deserialize)]

site/src/benchmark_metadata/mod.rs

@@ -13,6 +13,7 @@ pub use metadata::ProfileMetadata;
 pub struct CompileBenchmarkMetadata {
     pub perf_config: BenchmarkConfig,
     pub release_metadata: ProfileMetadata,
+    pub dev_metadata: ProfileMetadata,
 }
 
 /// The metadata of compile-time benchmarks is embedded directly within the binary using
@@ -50,6 +51,7 @@ fn load_compile_benchmark_metadata() -> HashMap<String, CompileBenchmarkMetadata
             let metadata::CompileBenchmarkMetadata {
                 perf_config,
                 release_metadata,
+                dev_metadata,
             } = metadata;
             let perf_config: BenchmarkConfig =
                 serde_json::from_value(perf_config).unwrap_or_else(|error| {
@@ -62,6 +64,7 @@ fn load_compile_benchmark_metadata() -> HashMap<String, CompileBenchmarkMetadata
             let metadata = CompileBenchmarkMetadata {
                 perf_config,
                 release_metadata,
+                dev_metadata,
             };
             (name, metadata)
         })