Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

benchmark suite for lix #76

Open
samuelstroschein opened this issue Sep 11, 2024 — with Linear · 5 comments
Open

benchmark suite for lix #76

samuelstroschein opened this issue Sep 11, 2024 — with Linear · 5 comments

Comments

Copy link
Member

samuelstroschein commented Sep 11, 2024

Context

We want lix to handle "larger" apps. SeeMESDK-137 for example.

Proposal

Implement a benchmark suite that is called in the test script to:

  • surface performance regressions
  • surface optimization potential

Metrics

@samuelstroschein samuelstroschein changed the title ensure that lix works with a project with 200.000 messages ensure that lix works with an inlang project with 200.000 messages Sep 11, 2024
@samuelstroschein samuelstroschein changed the title ensure that lix works with an inlang project with 200.000 messages ensure that lix works with an inlang project with 250.000 messages Sep 11, 2024
@samuelstroschein samuelstroschein changed the title ensure that lix works with an inlang project with 250.000 messages ensure that lix works with an inlang project with 250.000 variants Sep 11, 2024
Copy link
Member Author

We need to add a test for changes too. Prob saying something along the lines of each entity has 10 (?) changes to test scalability of lix.

250k variants * 10 changes each = 2.5 million changes

Copy link
Member Author

if we save changes in lix directly, avoiding diffing, no performance issues should arise because it's… just sqlite. The differ is the expensive operation.

the inlang sdk can write directly to the lix database. No need to diff :)

@samuelstroschein samuelstroschein changed the title ensure that lix works with an inlang project with 250.000 variants benchmark suite for lix Oct 8, 2024
Copy link
Member Author

I changed the title of this issue to benchmark suite to:

  • ensure that we have recurring benchmarks we test against
  • de-couple lix from inlang

Copy link
Member Author

@martin.lysk1 did you/will you merge the bench testing you've implemented?

Copy link

martin-lysk commented Oct 15, 2024

we cherrypick the getLeafChange (recursive) and its benchmarks - as examples

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

No branches or pull requests

2 participants