Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-9647

Improve subscriber scalability.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Current there is no batching for serving the subscribe requests. And constructing and generating the initial GET_STATE message is very expensive due to evolving and etc.

      Three perf traces are uploaded:

      During a scale test, we tested the scalability of concurrent subscribers. Three perf traces are collected:

      mesos-master_ui_p1.stacks.gz // baseline
      mesos-master_ui_p10.stacks.gz // added 10 more subscribers
      mesos-master_ui_p19.stacks.gz // add 19 subscribers

      At 19, slowness and timeouts are reported:

      "having a tough time getting a response from /mesos/api/v1?subscribe"
      "73s/100MB response time, now getting timeouts (504)"

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            mzhu Meng Zhu

            Dates

              Created:
              Updated:

              Slack

                Issue deployment