Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: Add ability to measure methods time execution

RCA Group

None

Description

During fixing OOM issue in SRS we saw that update operations processed longer, than create operation. It would be good to know which operations take how long. This will help to find places in code that need additional performance optimizations. 

Regarding approach - this code to measure performance should not be in our business code, as one option we can create new annotation @Timed and aspect that will process it and write in logs method's execution time, but other options also could be considered.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux March 13, 2023 at 6:57 AM

P3 issue; moving to Release "Not scheduled" to decrease current scope

Ann-Marie Breaux January 30, 2023 at 7:09 PM

Moved from Orchid to Poppy to decrease scope

Ann-Marie Breaux August 2, 2022 at 5:55 AM

Moving to Orchid to reduce Nolana scope

Olamide Kolawole May 6, 2022 at 4:32 PM

 I am onboard with those suggestions you made. Tracing vertx applications is not perfect but it will be better than having nothing.

Serhii_Nosko May 5, 2022 at 1:08 PM

Hi , actually showed us how he set up instrumentation and Jager tool locally to capture requests made to system in order to identify performance bottlenecks. We need to think regarding next steps how we can apply it by ourselves, maybe to include these changes to vagrant releases(and make them disabled for production usage) or create some instruction/documentation with setup steps, what do you think?

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Folijet

Parent

Release

Not Scheduled

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 18, 2021 at 1:26 PM
Updated March 13, 2023 at 6:57 AM
TestRail: Cases
TestRail: Runs