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

Evaluate the InfluxDB with SAL

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_aos
    • Labels:

      Description

      This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

      Compare the MariaDB quary language and InfluxDB quary language.

      Evaluation steps:

      1. Check with the AT CSC owners with the telemetry rate according to the page: https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson
      2. Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and opensplice version is 6.9.
      3. Change the test telemetry script to run infinity times (iseq in C++) with the correct telemetry frequency (delay_1s in C, the first argument is sec and the second is nano-sec).
      4. Run the test for SSD, NVME, and Disk.
      5. The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
      6. I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
      7. Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
      8. I can also do the above modifications by python.

        Attachments

        1. AT_owner
          0.5 kB
        2. AT_owner_update
          0.8 kB
        3. errorFromTclsh.log
          452 kB
        4. error img.png
          error img.png
          431 kB
        5. errorWhenBuildWriter.log
          39 kB

          Activity

          ttsai Te-Wei Tsai created issue -
          ttsai Te-Wei Tsai made changes -
          Field Original Value New Value
          Epic Link DM-18555 [ 244578 ]
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk. This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.
          This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:

          1. Check with the AT CSC owners with the telemetry rate according to the page of 
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:

          1. Check with the AT CSC owners with the telemetry rate according to the page of 
          This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           #
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           #
          This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           # Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and openslice version is 6.9.
           # Change the test telemetry script to run infinity times (iseq in C++) with the correct telemetry frequency (delay_1s in C++, the first argument is sec and the second is nano-sec).
           # Run the test for SSD, NVME, and Disk.
           # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
           # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
           # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
           # I can also do the above modifications by python.
          ttsai Te-Wei Tsai made changes -
          Status To Do [ 10001 ] In Progress [ 3 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner [ 37637 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37643 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37643 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37658 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37658 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37659 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37659 ]
          ttsai Te-Wei Tsai made changes -
          Attachment AT_owner_update [ 37660 ]
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           # Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and openslice version is 6.9.
           # Change the test telemetry script to run infinity times (iseq in C++) with the correct telemetry frequency (delay_1s in C++, the first argument is sec and the second is nano-sec).
           # Run the test for SSD, NVME, and Disk.
           # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
           # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
           # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
           # I can also do the above modifications by python.
          This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           # Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and opensplice version is 6.9.
           # Change the test telemetry script to run infinity times (iseq in C+) ++ with the correct telemetry frequency (delay_1s in C+, the first argument is sec and the second is nano-sec).
           # Run the test for SSD, NVME, and Disk.
           # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
           # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
           # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
           # I can also do the above modifications by python.
          ttsai Te-Wei Tsai made changes -
          Description This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           # Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and opensplice version is 6.9.
           # Change the test telemetry script to run infinity times (iseq in C+) ++ with the correct telemetry frequency (delay_1s in C+, the first argument is sec and the second is nano-sec).
           # Run the test for SSD, NVME, and Disk.
           # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
           # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
           # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
           # I can also do the above modifications by python.
          This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.

          Compare the MariaDB quary language and InfluxDB quary language.

          Evaluation steps:
           # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]
           # Clone the ts_sal repository to the /home/ttsai. Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and opensplice version is 6.9.
           # Change the test telemetry script to run infinity times (iseq in C++) with the correct telemetry frequency (delay_1s in C, the first argument is sec and the second is nano-sec).
           # Run the test for SSD, NVME, and Disk.
           # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.
           # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".
           # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.
           # I can also do the above modifications by python.
          ttsai Te-Wei Tsai made changes -
          Status In Progress [ 3 ] To Do [ 10001 ]
          ttsai Te-Wei Tsai made changes -
          Priority Major [ 3 ] Blocker [ 1 ]
          ttsai Te-Wei Tsai made changes -
          Attachment errorFromTclsh.log [ 37669 ]
          Attachment errorWhenBuildWriter.log [ 37670 ]
          ttsai Te-Wei Tsai made changes -
          Attachment error img.png [ 37671 ]
          ttsai Te-Wei Tsai made changes -
          Priority Blocker [ 1 ] Major [ 3 ]
          ttsai Te-Wei Tsai made changes -
          Status To Do [ 10001 ] In Progress [ 3 ]
          ttsai Te-Wei Tsai made changes -
          Reviewers Dave Mills [ dmills ]
          Status In Progress [ 3 ] In Review [ 10004 ]
          dmills Dave Mills made changes -
          Resolution Done [ 10000 ]
          Status In Review [ 10004 ] Done [ 10002 ]

            People

            Assignee:
            ttsai Te-Wei Tsai
            Reporter:
            ttsai Te-Wei Tsai
            Reviewers:
            Dave Mills
            Watchers:
            Dave Mills, Te-Wei Tsai
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Start date:
              End date:

                Jenkins

                No builds found.