conbench-apache-arrow[bot] commented on PR #44925:
URL: https://github.com/apache/arrow/pull/44925#issuecomment-2518634277

   After merging your PR, Conbench analyzed the 3 benchmarking runs that have 
been run so far on merge-commit 2b5a80245d336e17ff149eca33e666fae71c04bf.
   
   There were 132 benchmark results with an error:
   
   - Commit Run on `arm64-t4g-2xlarge-linux` at [2024-12-04 
17:36:18Z](https://conbench.ursa.dev/compare/runs/8095de3a997b45b69ff8164ee4b304aa...2783a4eae1944cfca60141c768fcf41b/)
     - [`tpch` (R) with engine=arrow, format=parquet, language=R, 
memory_map=False, query_id=TPCH-07, 
scale_factor=1](https://conbench.ursa.dev/benchmark-results/06750a173e6f79bd80008d1d5b2901f3)
     - [`tpch` (R) with engine=arrow, format=native, language=R, 
memory_map=False, query_id=TPCH-09, 
scale_factor=1](https://conbench.ursa.dev/benchmark-results/06750a19ba29726f800014c5277268a5)
   - and 130 more (see the report linked below)
   
   There were 2 benchmark results indicating a performance regression:
   
   - Commit Run on `amd64-m5-4xlarge-linux` at [2024-12-04 
18:31:06Z](https://conbench.ursa.dev/compare/runs/229dc6d118ae42aea188a2000a3ed474...38d57a347ae741f89405b7a164a4d122/)
     - [`dataset-read` (Python) with async=True, 
dataset=nyctaxi_multi_parquet_s3, 
pre_buffer=true](https://conbench.ursa.dev/compare/benchmarks/067506e48fed7bb7800086e974e74cd9...06750a320bcd71da8000c033443b94ba)
     - [`dataset-read` (Python) with async=True, 
dataset=nyctaxi_multi_ipc_s3](https://conbench.ursa.dev/compare/benchmarks/067506ea66ca7533800041d8d2d35900...06750a37ff377db880009812d5156d33)
   
   The [full Conbench report](https://github.com/apache/arrow/runs/33940829043) 
has more details. It also includes information about 29 possible false 
positives for unstable benchmarks that are known to sometimes produce them.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to