Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1509

Measure & Document Read Performance

XMLWordPrintable

      Perform testing on CPS Core read (get and query) operations.

      Update CPS-Core Read & Write (large load) Test Results with results.

      • Tests run using test data from CPS-Core Read & Write (large load) Test Results
      • TBD which operations to be tested?
        • REST (Postman manual test, scripts to generate data)
          • Include data conversion and REST overhead, parallelism
          • org.onap.cps.rest.controller.DataRestController#getNodeByDataspaceAndAnchorV2
          • org.onap.cps.rest.controller.QueryRestController#getNodesByDataspaceAndAnchorAndCpsPathV2
        • Java (smaller more detailed parts of function)
          • Use the (new) performance-integration module
          • Insert dat in the (base)test
          • Prefer to use 'bookstore' and/or Ahila's model & Data

      A/C:

      1. Add Prometheus instrumentation for get and query controller methods and 'significant' ri-methods involved in these use cases
      2. Report measurement and share with team
        1. consider root v. non-root scenarios
        2. consider parallel client requests 
        3. consider leaf-condition query (or cpsPath query functionality is not yet in scope)
      3. Report suspect bottlenecks

       

      Additional Tasks

      1. Create Base Performance Test using Ahila's Data by extending integration-test/src/test/groovy/org/onap/cps/integration/base/CpsIntegrationSpecBase.groovy
      2. Create & Document PostMan REST collection

            danielhanrahan Daniel Hanrahan
            danielhanrahan Daniel Hanrahan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: