Needs Performance Check label

Hi all,

We would like start using the NeedsPerformanceCheck label to mark tickets that could slow down the system (UI or/and backend) to verify that after changes would be provided the performance will be on the same level or even better.

In this way we would like to start monitoring what changes cause performance issues and a developer that provided changes would decide if required changes to improve performance should be provided in the same ticket - because there a small number of changes - or in a new one if task is too big to accomplish - because the latest changes not always cause system slowdown, sometimes they only show it.

I marked the OLMIS-4599 with the new label because we are going to add a new endpoint to the system and because there is a performance acceptance criteria.

Feel free to post your opinions/suggestions about using the label.

Regards,

Lukasz


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

···

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com

Hi Łukasz,

I wonder what should be the criteria for adding NeedsPerformanceCheck label to ticket. Should we document it somewhere?

Also, is this label a hint for QA to check performance manually or for developer to add some automated performance tests?

Best regards,

Paweł


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

···

On Fri, Apr 27, 2018 at 9:49 AM, Łukasz Lewczyński llewczynski@soldevelo.com wrote:

Hi all,

We would like start using the NeedsPerformanceCheck label to mark tickets that could slow down the system (UI or/and backend) to verify that after changes would be provided the performance will be on the same level or even better.

In this way we would like to start monitoring what changes cause performance issues and a developer that provided changes would decide if required changes to improve performance should be provided in the same ticket - because there a small number of changes - or in a new one if task is too big to accomplish - because the latest changes not always cause system slowdown, sometimes they only show it.

I marked the OLMIS-4599 with the new label because we are going to add a new endpoint to the system and because there is a performance acceptance criteria.

Feel free to post your opinions/suggestions about using the label.

Regards,

Lukasz

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53z91uM%3DPPQoSZbsQN-6iB2mGGLVxbKUycem6n-x6OcF3w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Paweł Albecki

    Software Developer

     palbecki@soldevelo.com

Hi Pawel,

I would say we should add the label to any ticket that changes could slow down the system. I am not sure if we have any wiki page about labels.

I think this is for both QA and developer. I mean both sides should verify that performance is on the same level or better. The developer should think how to provide changes in the way that the system would work fine and the QA should verify that the performance is okay.

Regards,

Lukasz


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

···

On Mon, Apr 30, 2018 at 4:17 PM, Paweł Albecki palbecki@soldevelo.com wrote:

Hi Łukasz,

I wonder what should be the criteria for adding NeedsPerformanceCheck label to ticket. Should we document it somewhere?

Also, is this label a hint for QA to check performance manually or for developer to add some automated performance tests?

Best regards,

Paweł

**
SolDevelo** Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com

On Fri, Apr 27, 2018 at 9:49 AM, Łukasz Lewczyński llewczynski@soldevelo.com wrote:

Hi all,

We would like start using the NeedsPerformanceCheck label to mark tickets that could slow down the system (UI or/and backend) to verify that after changes would be provided the performance will be on the same level or even better.

In this way we would like to start monitoring what changes cause performance issues and a developer that provided changes would decide if required changes to improve performance should be provided in the same ticket - because there a small number of changes - or in a new one if task is too big to accomplish - because the latest changes not always cause system slowdown, sometimes they only show it.

I marked the OLMIS-4599 with the new label because we are going to add a new endpoint to the system and because there is a performance acceptance criteria.

Feel free to post your opinions/suggestions about using the label.

Regards,

Lukasz

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com

**
SolDevelo** Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53z91uM%3DPPQoSZbsQN-6iB2mGGLVxbKUycem6n-x6OcF3w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Paweł Albecki

    Software Developer

     palbecki@soldevelo.com

Hi Pawel,

I would say we should add the label to any ticket that changes could slow down the system. I am not sure if we have any wiki page about labels.

I think this is for both QA and developer. I mean both sides should verify that performance is on the same level or better. The developer should think how to provide changes in the way that the system would work fine and the QA should verify that the performance is okay.

Regards,
Lukasz

Lukasz,
We do have an outline of how to fill out a ticket here : https://openlmis.atlassian.net/wiki/spaces/OP/pages/57409539/Software+Development+Methodology#SoftwareDevelopmentMethodology-TicketTypes however it doesn’t list out all the labels we use and why. We could add a list with reasons. Where do you think it would make sense to start populating that list? Do devs check this wiki page or should it be somewhere else?

Thanks,
Mary Jo

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com<mailto:llewczynski@soldevelo.com>

···

From: OpenLMIS Dev <openlmis-dev@googlegroups.com> on behalf of Łukasz Lewczyński <llewczynski@soldevelo.com>
Date: Tuesday, May 1, 2018 at 10:44 PM
To: Paweł Albecki <palbecki@soldevelo.com>
Cc: OpenLMIS Dev <openlmis-dev@googlegroups.com>
Subject: Re: [openlmis-dev] Needs Performance Check label

On Mon, Apr 30, 2018 at 4:17 PM, Paweł Albecki <palbecki@soldevelo.com<mailto:palbecki@soldevelo.com>> wrote:
Hi Łukasz,

I wonder what should be the criteria for adding NeedsPerformanceCheck label to ticket. Should we document it somewhere?
Also, is this label a hint for QA to check performance manually or for developer to add some automated performance tests?

Best regards,
Paweł

On Fri, Apr 27, 2018 at 9:49 AM, Łukasz Lewczyński <llewczynski@soldevelo.com<mailto:llewczynski@soldevelo.com>> wrote:
Hi all,

We would like start using the NeedsPerformanceCheck label to mark tickets that could slow down the system (UI or/and backend) to verify that after changes would be provided the performance will be on the same level or even better.

In this way we would like to start monitoring what changes cause performance issues and a developer that provided changes would decide if required changes to improve performance should be provided in the same ticket - because there a small number of changes - or in a new one if task is too big to accomplish - because the latest changes not always cause system slowdown, sometimes they only show it.

I marked the OLMIS-4599 with the new label because we are going to add a new endpoint to the system and because there is a performance acceptance criteria.

Feel free to post your opinions/suggestions about using the label.

Regards,
Lukasz

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com<mailto:llewczynski@soldevelo.com>

Error! Filename not specified.
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com<http://www.soldevelo.com>
Al. Zwycięstwa 96<https://maps.google.com/?q=Al.+Zwycięstwa+96&entry=gmail&source=g>/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com<mailto:openlmis-dev+unsubscribe@googlegroups.com>.
To post to this group, send email to openlmis-dev@googlegroups.com<mailto:openlmis-dev@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53z91uM%3DPPQoSZbsQN-6iB2mGGLVxbKUycem6n-x6OcF3w%40mail.gmail.com<https://groups.google.com/d/msgid/openlmis-dev/CAAdp53z91uM%3DPPQoSZbsQN-6iB2mGGLVxbKUycem6n-x6OcF3w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--

Paweł Albecki
Software Developer
palbecki@soldevelo.com<mailto:%20palbecki@soldevelo.com%20>

Error! Filename not specified.
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com<http://www.soldevelo.com>
Al. Zwycięstwa 96<https://maps.google.com/?q=Al.+Zwycięstwa+96&entry=gmail&source=g>/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

[Image removed by sender.]
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com<http://www.soldevelo.com>
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com<mailto:openlmis-dev+unsubscribe@googlegroups.com>.
To post to this group, send email to openlmis-dev@googlegroups.com<mailto:openlmis-dev@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53wpUpboNf9uTjjD_%2BD%2Ba045F_vxj1%3D-8_upcqATsUeVKw%40mail.gmail.com<https://groups.google.com/d/msgid/openlmis-dev/CAAdp53wpUpboNf9uTjjD_%2BD%2Ba045F_vxj1%3D-8_upcqATsUeVKw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

Hi Mary Jo,

I think we could update the wiki page that you shown. From what I see there are information about ticket type, fields, workflow so we could add information about labels that we use.

Regards,

Lukasz


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

···

On Wed, May 2, 2018 at 4:43 PM, Mary Jo Kochendorfer maryjo.kochendorfer@villagereach.org wrote:

From: OpenLMIS Dev openlmis-dev@googlegroups.com on behalf of Łukasz Lewczyński llewczynski@soldevelo.com

Date: Tuesday, May 1, 2018 at 10:44 PM

To: Paweł Albecki palbecki@soldevelo.com

Cc: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: Re: [openlmis-dev] Needs Performance Check label

Hi Pawel,

I would say we should add the label to any ticket that changes could slow down the system. I am not sure if we have any wiki page about labels.

I think this is for both QA and developer. I mean both sides should verify that performance is on the same level or better. The developer should think how to provide changes in the way that the system would work fine and the QA should verify that the performance is okay.

Regards,

Lukasz

Lukasz,

We do have an outline of how to fill out a ticket here : https://openlmis.atlassian.net/wiki/spaces/OP/pages/57409539/Software+Development+Methodology#SoftwareDevelopmentMethodology-TicketTypes
however it doesn’t list out all the labels we use and why. We could add a list with reasons. Where do you think it would make sense to start populating that list? Do devs check this wiki page or should it be somewhere else?

Thanks,

Mary Jo

Łukasz Lewczyński

Software Developer

llewczynski@soldevelo.com

On Mon, Apr 30, 2018 at 4:17 PM, Paweł Albecki <palbecki@soldevelo.com > wrote:

Hi Łukasz,

I wonder what should be the criteria for adding NeedsPerformanceCheck label to ticket. Should we document it somewhere?

Also, is this label a hint for QA to check performance manually or for developer to add some automated performance tests?

Best regards,

Paweł

On Fri, Apr 27, 2018 at 9:49 AM, Łukasz Lewczyński <llewczynski@soldevelo.com > wrote:

Hi all,

We would like start using the NeedsPerformanceCheck label to mark tickets that could slow down the system (UI or/and backend) to verify that after changes would be provided the performance will be on the same level or even better.

In this way we would like to start monitoring what changes cause performance issues and a developer that provided changes would decide if required changes to improve performance should be provided in the same ticket - because there a small number of changes - or in a new one if task is too big to accomplish - because the latest changes not always cause system slowdown, sometimes they only show it.

I marked the OLMIS-4599 with the new label because we are going to add a new endpoint to the system and because there is a performance acceptance criteria.

Feel free to post your opinions/suggestions about using the label.

Regards,

Lukasz

Łukasz Lewczyński

Software Developer

llewczynski@soldevelo.com

Error! Filename not specified.**
SolDevelo** Sp. z o.o. [LLC] / www.soldevelo.com

Al. Zwycięstwa 96 /98, 81-451, Gdynia, Poland

Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to
openlmis-dev@googlegroups.com.

To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis-dev/CAAdp53z91uM%3DPPQoSZbsQN-6iB2mGGLVxbKUycem6n-x6OcF3w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Paweł Albecki

Software Developer

palbecki@soldevelo.com

Error! Filename not specified.**
SolDevelo** Sp. z o.o. [LLC] / www.soldevelo.com

Al. Zwycięstwa 96 /98, 81-451, Gdynia, Poland

Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

**

SolDevelo** Sp. z o.o. [LLC] / www.soldevelo.com

Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland

Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53wpUpboNf9uTjjD_%2BD%2Ba045F_vxj1%3D-8_upcqATsUeVKw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Łukasz Lewczyński
Software Developer
llewczynski@soldevelo.com