Tracker capture: Complete button performance decreased since 2.30

Dear users,

Since we have upgraded our system to version 2.30 we have observed that after clicking on the Complete button in**an event it takes longer to actually complete that event that it used to (it might take about 5 to 10 seconds from the moment we click the Complete button and the values actually turning to grey). I have tested it in DHIS2 2.30 play version but I see no disruption on performance. I was wondering if someone in here has ever experienced something similar.

Also simulated through command line (example for play server but also done in our instance):

curl -X PUT -H “Content-Type: application/json” https://play.dhis2.org/2.29/api/29/events/tAg4jQEL8Qv

The payload size in localinstance is quite similar to the one sending in play server (both attached). However while our TTFB is (for instance) over 6000ms in our local server, the play server is almost immediate. No different results observed after emptying our datavalue tables.

Any advice in terms of infrastucture is more than welcome.

Thanks,

Eric

localinstance_payload.json (810 Bytes)

play_payload.json (668 Bytes)

1 Like

Hi there Eric!

Is your 2.30 build more than 14 days old? We did some tracker client performance fixes on nov 14 and nov 16.

Markus

···
  1. nov. 2018 kl. 18:05 skrev Eric Barreda Prades ericbarredap@gmail.com:

Dear users,

Since we have upgraded our system to version 2.30 we have observed that after clicking on the Complete button in**an event it takes longer to actually complete that event that it used to (it might take about 5 to 10 seconds from the moment we click the Complete button and the values actually turning to grey). I have tested it in DHIS2 2.30 play version but I see no disruption on performance. I was wondering if someone in here has ever experienced something similar.

Also simulated through command line (example for play server but also done in our instance):

curl -X PUT -H “Content-Type: application/json” https://play.dhis2.org/2.29/api/29/events/tAg4jQEL8Qv

The payload size in localinstance is quite similar to the one sending in play server (both attached). However while our TTFB is (for instance) over 6000ms in our local server, the play server is almost immediate. No different results observed after emptying our datavalue tables.

Any advice in terms of infrastucture is more than welcome.

Thanks,

Eric

<localinstance_payload.json>

<play_payload.json>


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

1 Like

Hi Markus,

Thanks a lot for your quick response. Our build is quite updated:

Build revision:

47460e8

Build date:

2018-11-19 10:54

However to be fair I think that the process has speed up a little bit from our last build. Let me update our version to the latest build and see how is it going.

Yours,

Eric

···

El lun., 26 nov. 2018 a las 21:40, Markus Bekken (markus@dhis2.org) escribió:

Hi there Eric!
Is your 2.30 build more than 14 days old? We did some tracker client performance fixes on nov 14 and nov 16.

Markus

  1. nov. 2018 kl. 18:05 skrev Eric Barreda Prades ericbarredap@gmail.com:

Dear users,

Since we have upgraded our system to version 2.30 we have observed that after clicking on the Complete button in**an event it takes longer to actually complete that event that it used to (it might take about 5 to 10 seconds from the moment we click the Complete button and the values actually turning to grey). I have tested it in DHIS2 2.30 play version but I see no disruption on performance. I was wondering if someone in here has ever experienced something similar.

Also simulated through command line (example for play server but also done in our instance):

curl -X PUT -H “Content-Type: application/json” https://play.dhis2.org/2.29/api/29/events/tAg4jQEL8Qv

The payload size in localinstance is quite similar to the one sending in play server (both attached). However while our TTFB is (for instance) over 6000ms in our local server, the play server is almost immediate. No different results observed after emptying our datavalue tables.

Any advice in terms of infrastucture is more than welcome.

Thanks,

Eric

<localinstance_payload.json>

<play_payload.json>


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

1 Like

Hi Eric & Markus,

We’re also experiencing the same performance issue, plus others related to the program rules. Please see here the Jira issue that we created for this:

https://jira.dhis2.org/browse/DHIS2-5259

(BTW, we’ve also tested with yesterday build from Jenkins that improved a bit but still far from what we had in 2.28)

Thank you in advance for your help.

Best regards

Le mar. 27 nov. 2018 à 09:29, Eric Barreda Prades ericbarredap@gmail.com a écrit :

···

Ignacio Foche Pérez

1 Like

Thanks!
The performance fixes two weeks ago was mainly on the rendering speed and not specifically on the rules which was perfomant in our test enviroment. We will look into the issue linked by ignacio below.

Markus

···

Ignacio Foche Pérez

1 Like

Hi Markus,

We’ve switched to build 2018-12-04 02:06. Although the performance has increased, it is a bit slow still. I’m sorry I am not specific at all and I know that this is quite annoying for you, but any recomendations you may have in terms of configuration that could help us improve the performance of our system would be helpful.

Thanks,

Eric

1 Like

Dear @barreda,
your feedback is very valuable. I am glad to hear about the relative performance increase, but want to know as much as possible about the current slowness you are experiencing. If you could add a description to this issue: DHIS2-5259

Anything you can describe about which operations/clicks that takes time is valuable, and please also include metrics on your program - how many program stages, data elements, program rules and tracked entity attributes are used.

Markus

1 Like