Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-28253

Optimize memory allocations in DB flows

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Central
    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • Rox Sprint 4.8G - Global
    • 0

      Optimize memory allocation and lower the pressure on GC by preferring stack allocation over heap allocation, optimise handling multiple results from DB with callback/iterator over slice. [Design doc by tjanisze@redhat.com](https://docs.google.com/document/d/1OU9ZK-uvoUFK_exLXyGBvC2-hqnD2pS4xrWEyeR0gms/edit?tab=t.0#heading=h.z1kxbq66s4k)

          1.
          		 Use Walk instead of GetAll Sub-task Closed Undefined Tomasz Janiszewski
          2.
          		 Add Walk to the auth provider store interface Sub-task Closed Undefined Tomasz Janiszewski
          3.
          		 Create GetByQueryFn and deprecate GetByQuery Sub-task Closed Undefined Tomasz Janiszewski
          4.
          		 Use GetByQueryFn instead of GetByQuery Sub-task Backlog Undefined Unassigned
          5.
          		 Create GetByIDs and use it instead of GetMany Sub-task Backlog Undefined Tomasz Janiszewski
          6.
          		 cleanup Store interface with variadic args Sub-task Backlog Undefined Unassigned
          7.
          		 Define when to use cursors Sub-task Backlog Undefined Unassigned
          8.
          		 Create Fn functions in Alerts datastore Sub-task Backlog Undefined Unassigned

              Unassigned Unassigned
              aruklets@redhat.com Alexander Rukletsov
              ACS Sensor & Ecosystem
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: