dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

A stack trace (at least) from the server when you are performing the
operation would be required so the developers can see what the problem
is. Also, information on the revision and database version would be useful.

Possibly the provision of a log-in on the server to the development team as
well, or alternatively, a copy of the database may also be needed.





On Fri, Sep 18, 2015 at 11:01 AM, Calle Hedberg <calle.hedberg@xxxxxxxxx>
wrote:

> Jason,
>
> Can you be more specific when you say this bug report is incomplete, i.e.
> what additional information you require?
> Calle
>
> On 18 September 2015 at 11:17, jason.p.pickering <
> 1490174@xxxxxxxxxxxxxxxxxx
> > wrote:
>
> > ** Changed in: dhis2
> >        Status: New => Incomplete
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1490174
> >
> > Title:
> >   Deleting Data Elements in UI very slow / hanging
> >
> > Status in DHIS:
> >   Incomplete
> >
> > Bug description:
> >   I have observed this behaviour multiple times now (2.18 and 2.19:
> >
> >   When deleting data elements from the data element list, the process is
> >   unreasonably slow (2-8 minutes) on a relatively slow connection (in
> >   this case I'm using a basic 1mbits connection in Norway running into a
> >   Cape Town server) AND in most cases the "progress bar message"
> >   DELETING..... is never replaced by the "Object deleted" message.
> >
> >   When deleting similar data elements from a local instance, it takes
> >   around 15 seconds. This is also relatively slow, in particular since
> >   the most demanding lookup into the datavalue table only takes around 1
> >   second running as a separate pgSQL query - which leads me to suspect
> >   that there is some inefficient code (nested query or similar) in the
> >   delete DE sequence.
> >
> >   With a slow connection, it seems like the DE delete sequence takes so
> >   long that some kind of time-out takes place.
> >
> >   In some cases, refreshing the browser page will show that the deleted
> >   DE is gone - in other cases the browser (cache) still shows the DE is
> >   there, whereas  checking the server instance via pgremote shows the DE
> >   has indeed been deleted. If the refresh button is hit too early - let
> >   us say within 1-2 minutes - there's no change in the database.
> >
> >   Note that I have only observed this low performance / tendency to
> >   "hang" when deleting Data Elements - all other deletions seems to be
> >   quick.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/dhis2/+bug/1490174/+subscriptions
> >
>
>
> --
>
> *******************************************
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472
>
> Cell: +27-82-853-5352
>
> Iridium SatPhone: +8816-315-19119
>
> Email: calle.hedberg@xxxxxxxxx
>
> Skype: calle_hedberg
>
> *******************************************
>
> --
> You received this bug notification because you are a member of DHIS 2
> developers, which is subscribed to DHIS.
> https://bugs.launchpad.net/bugs/1490174
>
> Title:
>   Deleting Data Elements in UI very slow / hanging
>
> Status in DHIS:
>   Incomplete
>
> Bug description:
>   I have observed this behaviour multiple times now (2.18 and 2.19:
>
>   When deleting data elements from the data element list, the process is
>   unreasonably slow (2-8 minutes) on a relatively slow connection (in
>   this case I'm using a basic 1mbits connection in Norway running into a
>   Cape Town server) AND in most cases the "progress bar message"
>   DELETING..... is never replaced by the "Object deleted" message.
>
>   When deleting similar data elements from a local instance, it takes
>   around 15 seconds. This is also relatively slow, in particular since
>   the most demanding lookup into the datavalue table only takes around 1
>   second running as a separate pgSQL query - which leads me to suspect
>   that there is some inefficient code (nested query or similar) in the
>   delete DE sequence.
>
>   With a slow connection, it seems like the DE delete sequence takes so
>   long that some kind of time-out takes place.
>
>   In some cases, refreshing the browser page will show that the deleted
>   DE is gone - in other cases the browser (cache) still shows the DE is
>   there, whereas  checking the server instance via pgremote shows the DE
>   has indeed been deleted. If the refresh button is hit too early - let
>   us say within 1-2 minutes - there's no change in the database.
>
>   Note that I have only observed this low performance / tendency to
>   "hang" when deleting Data Elements - all other deletions seems to be
>   quick.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dhis2/+bug/1490174/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049