Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-14554

[fiware-stackoverflow] Fiware Orion performance variations

    Details

      Description

      Created question in FIWARE Q/A platform on 24-08-2018 at 11:08
      Please, ANSWER this question AT https://stackoverflow.com/questions/52001855/fiware-orion-performance-variations

      Question:
      Fiware Orion performance variations

      Description:
      I need advice on matter of performance.

      Issue is that posting exact same data to Fiware Orion with only difference being Fiware-Service path result in exponential increase in times. Meaning each next request take more time than first and keep on adding.

      My program read and parse some files then store that into Fiware Orion, depending on file size it take up to max 3 seconds to do checks and parsing.
      Then that data is being send to Orion Context Broker.

      Example:

      Empty and fresh instance of Orion
      Test case here is 3000 entities, POST using batch operations.
      Because of size of entities that 3000 are being cut into smaller sizes and send to Orion with batch. In this case my program will cut them into size of 500 and send them one after another.
      First run 3000 entities time for completing operations 7 second.
      Change service path run same 3000 entities time for completing operation 14/15 seconds.
      Change service path run same 3000 entities time for completing operation 20 + seconds.
      etc..

      My instance of Fiware is being run using docker-compose commands used for Fiware/Mongo:

      -dbhost mongo -reqMutexPolicy none -dbPoolSize 100 -logLevel NONE

      --nojournal --logappend

      I need advice on this since i didn't found specific info about this type of issue (if i missed please just point me to it). For me it seem like something is with mongo making it behave strange. Or could it be i am making some mistake.

      { id: "8B56C6",
      type: "DepositPoint",
      family: { value: "Agent", type: "String", metadata: {} },
      serialNumber: { value: "", type: "String", metadata: {} },
      refSortingType: { value: "sortingtype:2", type: "String", metadata: {} },
      description: { value: "", type: "String", metadata: {} },
      refType: { value: "depositpointtype:0", type: "String", metadata: {} },
      storedWasteOrigin: { value: "", type: "String", metadata: {} },
      location:
      { value:

      { type: "Point", coordinates: [Array] }

      ,
      type: "geo:json" },
      address: { value: "", type: "String", metadata: {} },
      fillingLevel:

      { value: 0, type: "Integer" }

      ,
      cargoWeight: { value: 0, type: "Integer", metadata:

      { unit: [Object] }

      },
      temperature: { value: 0, type: "Integer", metadata:

      { unit: [Object] }

      },
      methaneConcentration: { value: 0, type: "Integer", metadata:

      { unit: [Object] }

      },
      regulation: { value: "Municipal association", type: "String", metadata: {} },
      responsible: { value: "", type: "String", metadata: {} },
      owner: { value: "Txorierri", type: "String", metadata: {} },
      dateServiceStarted: { value: "", type: "String", metadata: {} },
      dateLastEmptying: { value: "", type: "String", metadata: {} },
      nextActuationDeadline: { value: "", type: "String", metadata: {} },
      actuationHours: { value: "", type: "String", metadata: {} },
      openingHours: { value: "", type: "String", metadata: {} },
      dateLastCleaning: { value: "", type: "String", metadata: {} },
      nextCleaningDeadline: { value: "", type: "String", metadata: {} },
      refDepositPointIsle: { value: "", type: "String", metadata: {} },
      status: { value: "ok", type: "String", metadata: {} },
      color: { value: "", type: "String", metadata: {} },
      image: { value: "", type: "String", metadata: {} },
      annotations: { value: "", type: "String", metadata: {} },
      areaServed: { value: "", type: "String", metadata: {} },
      dateModified: { value: "", type: "String", metadata: {} },
      refDevice: { value: "", type: "String", metadata: {} } }

      I re post this since same question got deleted without any reason. Hope it is clear.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        18d 20h 29m 1 Jose Manuel Cantera 12/Sep/18 8:35 AM
        In Progress In Progress Answered Answered
        1s 1 Jose Manuel Cantera 12/Sep/18 8:35 AM
        Answered Answered Closed Closed
        6d 13h 3m 1 Jose Manuel Cantera 18/Sep/18 9:38 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        jmcantera Jose Manuel Cantera made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        jmcantera Jose Manuel Cantera made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        jmcantera Jose Manuel Cantera made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        Description
        Created question in FIWARE Q/A platform on 24-08-2018 at 11:08
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/52001855/fiware-orion-performance-variations


        +Question:+
        Fiware Orion performance variations

        +Description:+
        I need advice on matter of performance.

        Issue is that posting exact same data to Fiware Orion with only difference being Fiware-Service path result in exponential increase in times. Meaning each next request take more time than first and keep on adding.

        My program read and parse some files then store that into Fiware Orion, depending on file size it take up to max 3 seconds to do checks and parsing.
        Then that data is being send to Orion Context Broker.

        Example:


        Empty and fresh instance of Orion
        Test case here is 3000 entities, POST using batch operations.
        Because of size of entities that 3000 are being cut into smaller sizes and send to Orion with batch. In this case my program will cut them into size of 500 and send them one after another.
        First run 3000 entities time for completing operations 7 second.
        Change service path run same 3000 entities time for completing operation 14/15 seconds.
        Change service path run same 3000 entities time for completing operation 20 + seconds.
        etc..


        My instance of Fiware is being run using docker-compose commands used for Fiware/Mongo:

        -dbhost mongo -reqMutexPolicy none -dbPoolSize 100 -logLevel NONE

        --nojournal --logappend

        I need advice on this since i didn't found specific info about this type of issue (if i missed please just point me to it). For me it seem like something is with mongo making it behave strange. Or could it be i am making some mistake.

        { id: "8B56C6",
        type: "DepositPoint",
        family: { value: "Agent", type: "String", metadata: {} },
        serialNumber: { value: "", type: "String", metadata: {} },
        refSortingType: { value: "sortingtype:2", type: "String", metadata: {} },
        description: { value: "", type: "String", metadata: {} },
        refType: { value: "depositpointtype:0", type: "String", metadata: {} },
        storedWasteOrigin: { value: "", type: "String", metadata: {} },
        location:
        { value: { type: "Point", coordinates: [Array] },
         type: "geo:json" },
        address: { value: "", type: "String", metadata: {} },
        fillingLevel: { value: 0, type: "Integer" },
        cargoWeight: { value: 0, type: "Integer", metadata: { unit: [Object] } },
        temperature: { value: 0, type: "Integer", metadata: { unit: [Object] } },
        methaneConcentration: { value: 0, type: "Integer", metadata: { unit: [Object]
        } },
        regulation: { value: "Municipal association", type: "String", metadata: {} },
        responsible: { value: "", type: "String", metadata: {} },
        owner: { value: "Txorierri", type: "String", metadata: {} },
        dateServiceStarted: { value: "", type: "String", metadata: {} },
        dateLastEmptying: { value: "", type: "String", metadata: {} },
        nextActuationDeadline: { value: "", type: "String", metadata: {} },
        actuationHours: { value: "", type: "String", metadata: {} },
        openingHours: { value: "", type: "String", metadata: {} },
        dateLastCleaning: { value: "", type: "String", metadata: {} },
        nextCleaningDeadline: { value: "", type: "String", metadata: {} },
        refDepositPointIsle: { value: "", type: "String", metadata: {} },
        status: { value: "ok", type: "String", metadata: {} },
        color: { value: "", type: "String", metadata: {} },
        image: { value: "", type: "String", metadata: {} },
        annotations: { value: "", type: "String", metadata: {} },
        areaServed: { value: "", type: "String", metadata: {} },
        dateModified: { value: "", type: "String", metadata: {} },
        refDevice: { value: "", type: "String", metadata: {} } }


        I re post this since same question got deleted without any reason. Hope it is clear.
        Created question in FIWARE Q/A platform on 24-08-2018 at 11:08
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/52001855/fiware-orion-performance-variations


        +Question:+
        Fiware Orion performance variations

        +Description:+
        I need advice on matter of performance.

        Issue is that posting exact same data to Fiware Orion with only difference being Fiware-Service path result in exponential increase in times. Meaning each next request take more time than first and keep on adding.

        My program read and parse some files then store that into Fiware Orion, depending on file size it take up to max 3 seconds to do checks and parsing.
        Then that data is being send to Orion Context Broker.

        Example:


        Empty and fresh instance of Orion
        Test case here is 3000 entities, POST using batch operations.
        Because of size of entities that 3000 are being cut into smaller sizes and send to Orion with batch. In this case my program will cut them into size of 500 and send them one after another.
        First run 3000 entities time for completing operations 7 second.
        Change service path run same 3000 entities time for completing operation 14/15 seconds.
        Change service path run same 3000 entities time for completing operation 20 + seconds.
        etc..


        My instance of Fiware is being run using docker-compose commands used for Fiware/Mongo:

        -dbhost mongo -reqMutexPolicy none -dbPoolSize 100 -logLevel NONE

        --nojournal --logappend

        I need advice on this since i didn't found specific info about this type of issue (if i missed please just point me to it). For me it seem like something is with mongo making it behave strange. Or could it be i am making some mistake.

        { id: "8B56C6",
        type: "DepositPoint",
        family: { value: "Agent", type: "String", metadata: {} },
        serialNumber: { value: "", type: "String", metadata: {} },
        refSortingType: { value: "sortingtype:2", type: "String", metadata: {} },
        description: { value: "", type: "String", metadata: {} },
        refType: { value: "depositpointtype:0", type: "String", metadata: {} },
        storedWasteOrigin: { value: "", type: "String", metadata: {} },
        location:
        { value: { type: "Point", coordinates: [Array] },
         type: "geo:json" },
        address: { value: "", type: "String", metadata: {} },
        fillingLevel: { value: 0, type: "Integer" },
        cargoWeight: { value: 0, type: "Integer", metadata: { unit: [Object] } },
        temperature: { value: 0, type: "Integer", metadata: { unit: [Object] } },
        methaneConcentration: { value: 0, type: "Integer", metadata: { unit: [Object]
        } },
        regulation: { value: "Municipal association", type: "String", metadata: {} },
        responsible: { value: "", type: "String", metadata: {} },
        owner: { value: "Txorierri", type: "String", metadata: {} },
        dateServiceStarted: { value: "", type: "String", metadata: {} },
        dateLastEmptying: { value: "", type: "String", metadata: {} },
        nextActuationDeadline: { value: "", type: "String", metadata: {} },
        actuationHours: { value: "", type: "String", metadata: {} },
        openingHours: { value: "", type: "String", metadata: {} },
        dateLastCleaning: { value: "", type: "String", metadata: {} },
        nextCleaningDeadline: { value: "", type: "String", metadata: {} },
        refDepositPointIsle: { value: "", type: "String", metadata: {} },
        status: { value: "ok", type: "String", metadata: {} },
        color: { value: "", type: "String", metadata: {} },
        image: { value: "", type: "String", metadata: {} },
        annotations: { value: "", type: "String", metadata: {} },
        areaServed: { value: "", type: "String", metadata: {} },
        dateModified: { value: "", type: "String", metadata: {} },
        refDevice: { value: "", type: "String", metadata: {} } }


        I re post this since same question got deleted without any reason. Hope it is clear.
        veronika Veronika Vlnkova made changes -
        Assignee Jose Manuel Cantera [ jmcantera ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2018-08-24 12:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-08-24 12:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            jmcantera Jose Manuel Cantera
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: