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

Rundeck performance on 'Activity for this Job' pages #1547

Open
jds86930 opened this issue Nov 12, 2015 · 6 comments
Open

Rundeck performance on 'Activity for this Job' pages #1547

jds86930 opened this issue Nov 12, 2015 · 6 comments
Labels

Comments

@jds86930
Copy link

@jds86930 jds86930 commented Nov 12, 2015

Our rundeck instance has a lot of jobs & a lot of executions ('execution' table is about 1 million rows large). We were noticing that performance got really slow on some pages, such as the 'Activity for this Job' pages. We were able to improve page load time quite a lot by adding the indexes listed below. These indexes were successfully applied on a MySQL 5.6.23 database. I wanted to post them here in case they can help anyone else out, or in case the developers want to integrate them into rundeck.

create index WORKFLOW_STEP__ID on workflow_step(id);
create index WORKFLOW_WORKFLOW_STEP__WORKFLOW_COMMANDS_ID on workflow_workflow_step(workflow_commands_id);
create index EXECUTION__PROJECT__DATE_COMPLETED on execution(project, date_completed);
create index EXECUTION__DATE_COMPLETED__SCHEDULED_EXECUTION_ID on execution(date_completed, scheduled_execution_id);
create index BASE_REPORT__CLASS__JC_JOB_ID__CTX_PROJECT on base_report(class, jc_job_id, ctx_project);

@jimr6007
Copy link

@jimr6007 jimr6007 commented Apr 20, 2016

I have been using http://rundeck.org/2.6.3/api/index.html#delete-an-execution
to cleanup my stuff but I also have 1 million plus rows in workflow and friends tables

I ended up here for the same reason, super slow "Activity for this Job" tabs on the UI

very annoying when you want to look at the last 10 executions for a job.

Any advice from the Rundeck people ?

Thanks !

@jds86930
Copy link
Author

@jds86930 jds86930 commented Apr 21, 2016

Haven't seen any followup on it from the rundeck devs. We're still successfully using the indexes listed in the original post, which cut the time down by 10x for us. It'd be nice if they'd integrate that into rundeck (or otherwise optimize the queries and/or data model), but at least this isn't crippling us anymore.

@truppert
Copy link

@truppert truppert commented Jan 4, 2017

This is awesome! I also saw a huge increase in speed by applying these. The Rundeck folks should really integrate this.

@nickrowlandboxuk
Copy link

@nickrowlandboxuk nickrowlandboxuk commented Feb 16, 2017

We're running version 2.6.4-1 of Rundeck. Is this still an issue the current version?

Thanks for sharing this fix. We've seen a massive improvement in page load speed.

@zsoca8711
Copy link

@zsoca8711 zsoca8711 commented Aug 11, 2017

We have applied these indexes too on our Rundeck 2.7.3-1 and the improvement is massive.

@stale
Copy link

@stale stale bot commented Apr 3, 2020

In an effort to focus on bugs and issues that impact currently supported versions of Rundeck, we have elected to notify GitHub issue creators if their issue is classified as stale and close the issue. An issue is identified as stale when there have been no new comments, responses or other activity within the last 12 months. If a closed issue is still present please feel free to open a new Issue against the current version and we will review it. If you are an enterprise customer, please contact your Rundeck Support to assist in your request.
Thank you, The Rundeck Team

@stale stale bot added the wontfix:stale label Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.