Details

    • Milestone
    • Status: Unplanned
    • Major
    • Resolution: Unresolved
    • None
    • F16
    • Planning
    • 3

    Description

      Refreshed, complete design of database system capable of supporting Alert Production and Level 1 user database. Details are described in ยง4.3 of LSE-163.

      Attachments

        Issue Links

          Activity

            Note, EPO has dependency on that milestone (Nightly transfers (LSE-131, 2.5,8 & LSE-89 1.1.2-3,3.8)), so we should make it a Level 2 milestone.

            jbecla Jacek Becla (Inactive) added a comment - Note, EPO has dependency on that milestone (Nightly transfers (LSE-131, 2.5,8 & LSE-89 1.1.2-3,3.8)), so we should make it a Level 2 milestone.
            fritzm Fritz Mueller added a comment - - edited

            It has been harder to meet the performance goals of the original design than was anticipated (more specifically, database query throughput for light-curve retrieval simultaneous with dense record insertion).

            We have built a functional prototype, but only to a limited scale. Discussion is needed to decide whether requirements should be relaxed (light curve query latencies and/or insertion latencies), or whether the requirements as currently stated hold and we should continue to search for a breakthrough in implementation.

            An additional factor in the delay of completion of this milestone was that the primary developer (Andy S) was re-assigned to SuperTask work items which were perceived to have hight priority since the L1/AP db was not at that time on the critical path.

            fritzm Fritz Mueller added a comment - - edited It has been harder to meet the performance goals of the original design than was anticipated (more specifically, database query throughput for light-curve retrieval simultaneous with dense record insertion). We have built a functional prototype, but only to a limited scale. Discussion is needed to decide whether requirements should be relaxed (light curve query latencies and/or insertion latencies), or whether the requirements as currently stated hold and we should continue to search for a breakthrough in implementation. An additional factor in the delay of completion of this milestone was that the primary developer (Andy S) was re-assigned to SuperTask work items which were perceived to have hight priority since the L1/AP db was not at that time on the critical path.

            People

              fritzm Fritz Mueller
              jbecla Jacek Becla (Inactive)
              Andy Salnikov, Ben Emmons [X] (Inactive), Eric Bellm, Fritz Mueller, Gregory Dubois-Felsmann, Jacek Becla (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Jenkins

                  No builds found.