perf(telemetry): Do not allocate lambda in fast-path

This commit changes the lookup for host and server aggregators to use
`getOrPut` instead of `computeIfAbsent`. The former will inline the
lambda and not cause any memory allocation in the fast-path (e.g., the
key exists), while the latter always allocates lambda for constructing
the aggregator.

1 files changed, 2 insertions, 2 deletions

diff --git a/opendc-telemetry/opendc-telemetry-compute/src/main/kotlin/org/opendc/telemetry/compute/ComputeMetricAggregator.kt b/opendc-telemetry/opendc-telemetry-compute/src/main/kotlin/org/opendc/telemetry/compute/ComputeMetricAggregator.kt
index 738ec38b..d5257bbd 100644
--- a/opendc-telemetry/opendc-telemetry-compute/src/main/kotlin/org/opendc/telemetry/compute/ComputeMetricAggregator.kt
+++ b/opendc-telemetry/opendc-telemetry-compute/src/main/kotlin/org/opendc/telemetry/compute/ComputeMetricAggregator.kt
@@ -222,7 +222,7 @@ public class ComputeMetricAggregator {
     private fun getHost(hosts: MutableMap<String, HostAggregator>, resource: Resource): HostAggregator? {
         val id = resource.attributes[HOST_ID]
         return if (id != null) {
-            hosts.computeIfAbsent(id) { HostAggregator(resource) }
+            hosts.getOrPut(id) { HostAggregator(resource) }
         } else {
             null
         }
@@ -234,7 +234,7 @@ public class ComputeMetricAggregator {
     private fun getServer(servers: MutableMap<String, ServerAggregator>, point: PointData): ServerAggregator? {
         val id = point.attributes[ResourceAttributes.HOST_ID]
         return if (id != null) {
-            servers.computeIfAbsent(id) { ServerAggregator(point.attributes) }
+            servers.getOrPut(id) { ServerAggregator(point.attributes) }
         } else {
             null
         }