Skip to content

Performance issues with latest mongodb package #41

@NickRycar

Description

@NickRycar

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions