Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-28154

Test APDB Cassandra prototype with 6 server nodes

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Story Points:
      8
    • Epic Link:
    • Sprint:
      DB_S21_12
    • Team:
      Data Access and Database
    • Urgent?:
      No

      Description

      With a baseline established by DM-28136 it's time to move and see how things scale with the extended cluster size. For this round of tests I want to use 6 nodes on server side, nodes are identical to the one already defined, I don't want very large data set yet with the existing SSD config we should be OK to run ~120k visits.

        Attachments

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-28136 Reproduce PDAC APDB tests with GCP

          • Done
          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-28172 Test APDB Cassandra prototype with 12 server nodes

          • Done
          links to

          Web Link Jupyter notebook

            Activity

            Ascending order - Click to sort in descending order
            salnikov Andy Salnikov created issue -
            salnikov Andy Salnikov made changes -
            Field Original Value New Value
            Epic Link DM-27785 [ 442300 ]
            salnikov Andy Salnikov made changes -
            Link This issue is triggered by DM-28136 [ DM-28136 ]
            salnikov Andy Salnikov made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            salnikov Andy Salnikov made changes -
            Description With a baseline established by DM-28136 it's time to move and se how things scale with the extended cluster size. For this round of tests I want to use 6 nodes on server side, nodes are identical to the one already defined, I don't want very large data set yet with the existing SSD config we should be OK to run ~120k visits. With a baseline established by DM-28136 it's time to move and see how things scale with the extended cluster size. For this round of tests I want to use 6 nodes on server side, nodes are identical to the one already defined, I don't want very large data set yet with the existing SSD config we should be OK to run ~120k visits.
            salnikov Andy Salnikov made changes -
            Attachment apdb-gcp2-nb-time-store-fit.png [ 46809 ]
            Attachment apdb-gcp2-nb-cpu-time-select-fit.png [ 46810 ]
            Attachment apdb-gcp2-nb-time-select-fit.png [ 46811 ]
            Attachment apdb-gcp2-latency-diasource.png [ 46812 ]
            salnikov Andy Salnikov made changes -
            Attachment apdb-gcp3-nb-cpu-time-select-fit.png [ 46934 ]
            Attachment apdb-gcp3-nb-time-select-fit.png [ 46935 ]
            Attachment apdb-gcp3-nb-time-store-fit.png [ 46936 ]
            salnikov Andy Salnikov made changes -
            Attachment apdb-gcp3-system-loadaverage.png [ 46938 ]
            Attachment apdb-gcp3-latency-diaobjectlast.png [ 46939 ]
            salnikov Andy Salnikov made changes -
            Resolution Done [ 10000 ]
            Status In Progress [ 3 ] Done [ 10002 ]
            salnikov Andy Salnikov made changes -
            Story Points 6 8
            salnikov Andy Salnikov made changes -
            Link This issue is triggering DM-28172 [ DM-28172 ]
            salnikov Andy Salnikov made changes -
            Remote Link This issue links to "Jupyter notebook (Web Link)" [ 27403 ]

              People

              Assignee:
              salnikov Andy Salnikov
              Reporter:
              salnikov Andy Salnikov
              Watchers:
              Andy Salnikov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.