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

Optimize speed and stabilize the batch graph refresh memory usage #15897

Conversation

Ladas
Copy link
Contributor

@Ladas Ladas commented Aug 28, 2017

Optimize speed and stabilize the batch graph refresh memory usage

The refresh speed gain on a big environment(1.2M records) is about 10% and memory rise much less after the parsing step.

@Ladas
Copy link
Contributor Author

Ladas commented Aug 28, 2017

@miq-bot assign @agrare
@miq-bot add_label enhancement, performance

Optimize speed and mem peaks a bit doing removing attribute_index
elements as we go and building all_attribute_keys inline
Optimize serializable keys by preloading it into hash and only
calling serialize for columns that actually neeed it.
Use pg_types for building serializable_keys and extract pg_types
to init, so it's built only once.
@Ladas Ladas force-pushed the optimize_speed_stabilize_the_batch_graph_refresh_memory_usage branch from 383b5cf to 7e5091f Compare September 26, 2017 12:44
@miq-bot
Copy link
Member

miq-bot commented Sep 26, 2017

Checked commits Ladas/manageiq@59c7172~...7e5091f with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
5 files checked, 0 offenses detected
Everything looks fine. 🏆

Copy link
Member

@agrare agrare left a comment

Choose a reason for hiding this comment

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

LGTM

@agrare agrare merged commit a373229 into ManageIQ:master Sep 26, 2017
@agrare agrare added this to the Sprint 70 Ending Oct 2, 2017 milestone Sep 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants