Skip to content

Conversation

ArBridgeman
Copy link
Collaborator

@ArBridgeman ArBridgeman commented Aug 15, 2025

closes #211

Checklist

Note: If any of the items in the checklist are not relevant to your PR, leave the box unchecked.

For any Pull Request

Is the following correct:

  • the title of the Pull Request?
  • the title of the corresponding issue?
  • there are no other open Pull Requests for the same update/change?
  • that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

  • update the changelog?
  • update the implementation?
  • check coverage and add tests: unit tests and, if relevant, integration tests?
  • update the User Guide & other documentation?
  • resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

  • thought about version number (major, minor, patch)?
  • checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

ArBridgeman and others added 2 commits August 11, 2025 13:30
* Add parquet import and update documentation

---------

Co-authored-by: Torsten Kilias <[email protected]>
@ArBridgeman ArBridgeman force-pushed the feature/211-benchmark-test-import-from-parquet branch from 480285c to 833dafe Compare August 18, 2025 07:11
@ArBridgeman ArBridgeman force-pushed the feature/211-benchmark-test-import-from-parquet branch from 3396fab to 5371a3e Compare August 25, 2025 12:07
1.3755199900000434,
2.322247650999998,
2.1706722630000286,
7.116984646999981,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The imports outlier's don't look random, mostly the round before the last is slow. Maybe we force a flush to disk of the uncommitted data at this point, because we don't cleanup.

5.422284263999927,
5.473687115000075,
10.43289915999992,
5.8234761429999935
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again

6.998409852999998,
7.840330088999963,
7.807797928000014,
12.746238112000015,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again

2.009181237000007,
2.81157267399999,
2.7745194739999306,
7.796403220000002,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again

import_params={"columns": ["SALES_TIMESTAMP", "PRICE", "CUSTOMER_NAME"]},
)

benchmark.pedantic(func_to_be_measured, iterations=1, rounds=benchmark_specs.rounds)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw a setup or teardown parameter

setup (callable) –

A function to call right before calling the target function in the first iteration of every round.

teardown (callable) –

A function to call after the last iteration of every round.

https://share.google/HYkd8TJRkLTfIVe8H

Because we use iterations 1 and multiple rounds, we should be able to cleanup for each measurement

@ArBridgeman ArBridgeman force-pushed the develop branch 2 times, most recently from 1428eb4 to 6eed5a1 Compare September 15, 2025 08:19
Base automatically changed from develop to master September 15, 2025 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants