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

FEATURE: meilisearch or redis support vs RamDrive #351

Open
spirillen opened this issue Jan 12, 2024 · 0 comments
Open

FEATURE: meilisearch or redis support vs RamDrive #351

spirillen opened this issue Jan 12, 2024 · 0 comments

Comments

@spirillen
Copy link
Contributor

spirillen commented Jan 12, 2024

Description

Earlier I've documented how it is possible to setup and use a ramDrive to support the CSV test results data.

However, when you are using a SQL driven backend, you can not as easily do this, the most trustworthy way is using a RAM-driven DB like mailisearch (not elasticSearch, it is to heavy for most systems) or RedisServer as they only take up the space that is needed.

Current load over hours, after restarting @PyFunceble after broken connection to MariaDB

image

Cost:
image

Possible Solution

By using a no-sql backend we can:

  1. Read out the full db to the middleman (~550.000 records is about ~35MB)
    1.2. This will speed up the "--continue" and read in from source to first test
  2. for every X test results, it will keep trying writing these data to SQL backend until succees

Considered Alternative

Not for now

Additional context

Nope, be happy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants