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 issues with latest mongodb package #41

Open
NickRycar opened this issue Jul 2, 2019 · 4 comments
Open

Performance issues with latest mongodb package #41

NickRycar opened this issue Jul 2, 2019 · 4 comments
Labels
enhancement New feature or request

Comments

@NickRycar
Copy link

Recent builds of the core/mongodb package are significantly larger than previous builds had been, which causes a number of unintended consequences that affect the national parks demo:

  1. The time it takes to run a hab svc load core/mongodb can be quite long
  2. Running the package in a local studio (particularly the docker studio on mac) can fail in a difficult to diagnose way -- the supervisor never starts the service or any constituent services until the supervisor is terminated and relaunched.

The second bullet here is the real killer -- particularly because it's inconsistent. Sometimes bumping the memory allocation to docker can fix it, and sometimes not.

As a short-term solution, @jvogt called out that pinning to an earlier release, particularly core/mongodb/3.2.10/20171016003652, solves this issue.

The problem is on the hab team's radar, but low priority. Recommend we update configs to use this release for the time being to make demo life more manageable.

@NickRycar NickRycar added the enhancement New feature or request label Jul 2, 2019
@smford22
Copy link
Contributor

@ChefRycar have you started to use core/mongodb/3.2.10/20171016003652 when demoing NatParks? Could be a legit story, "When installing MongoDB into my studio I can specify the exact version that is running in prod..."

@NickRycar
Copy link
Author

@smford22 I have not. I only became aware when I described weird behavior I experienced in my analyst demo, and he was able to suss out the culprit. Haven't poked at it too much since, but I could definitely see a story there.

@jvogt outside of avoiding the odd supervisor behavior, what kind of time savings are we talking vs. the latest package?

Also, is there an issue open for core-plans on this? Should probably reference it somewhere too if so.

@smford22
Copy link
Contributor

@ChefRycar I have been testing today and it is significantly faster during the local dev story. Recently I had been doing demos by hab svc load core/mongodb before the demo began to cut time. With the version specified by @jvogt I can do that live again.

As for Terraform, there is a decent reduction in provision time as well. I will have a PR together shortly.

@NickRycar
Copy link
Author

Sweet!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants