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

Performance affected by size of database #77

Open
wreddin opened this issue Mar 30, 2018 · 3 comments
Open

Performance affected by size of database #77

wreddin opened this issue Mar 30, 2018 · 3 comments

Comments

@wreddin
Copy link

wreddin commented Mar 30, 2018

We are finding that the performance of the application is affected by the size of the database. When the database grows too large the UI becomes slow to render. This causes our automated tests to fail.

As a workaround, we have created a job that deletes messages that are more than 7 days old.

The approximate size of the database for which we saw performance issues is150k messages and 1.1mill headers.

@kblief
Copy link
Collaborator

kblief commented Mar 30, 2018

What database are you using? Is it the embedded h2?

There may be a need for some indexing on the database.

@wreddin
Copy link
Author

wreddin commented Mar 30, 2018

We are using MySQL.

@kblief
Copy link
Collaborator

kblief commented Mar 30, 2018

Can you, or someone in your organization, check the database for slow queries and missing indexes?

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