Pith. sign in

REVIEW 1 cited by

Overhead Measurement Noise in Different Runtime Environments

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 2411.05491 v1 pith:D4ZOYYIF submitted 2024-11-08 cs.PF

classification cs.PF
keywords executiondifferentenvironmentsmoobenchchangesoverheadperformancebenchmark
verification ladder T0 review T1 audit T2 compute T3 formal

Signed reviews

No signed human review yet.

0 comments
read the original abstract

In order to detect performance changes, measurements are performed with the same execution environment. In cloud environments, the noise from different processes running on the same cluster nodes might change measurement results and thereby make performance changes hard to measure. The benchmark MooBench determines the overhead of different observability tools and is executed continuously. In this study, we compare the suitability of different execution environments to benchmark the observability overhead using MooBench. To do so, we compare the execution times and standard deviation of MooBench in a cloud execution environment to three bare-metal execution environments. We find that bare metal servers have lower runtime and standard deviation for multi-threaded MooBench execution. Nevertheless, we see that performance changes up to 4.41% are detectable by GitHub actions, as long as only sequential workloads are examined.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. How Much Does It Cost to Answer My Question? Benchmarking Cloud VLM-based VQA Systems

    cs.CV 2026-08 conditional novelty 6.0 of 10

    Preprocessing effects on cloud VLM VQA vary strongly by model, API paradigm, and provider token accounting, so no single preprocessing strategy is universally best.

Pith tools