Project

General

Profile

Actions

Feature #39957

closed

mgr/dashboard: Resolve TestBed performance issue

Added by Anonymous almost 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Stephan Müller
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
mimic
Reviewed:
Affected Versions:
Pull request ID:

Description

With this helper function you can easily resolve the TestBed resetting
performance issue. If more tests exists in a test suite, it makes sense
to configure TestBed only once if you are not doing a lot of TestBed
specific stuff (haven't hit the limitation). It will reduce the test
run time by around $tests * 50 . In my case it was a test suite with
47 tests with a run time of over 30s after using the static test bed
method it ran in 1.2s. The run time was reduced to 0.04 %! This is
equivalent to a speed increase of 2500
(100/0.04)!

For our own security the normal way will be taken if you not
set the DEV configuration variable to true. It will be false when
"run-frontend-unittests.sh" is run.


Related issues 1 (0 open1 closed)

Copied to Dashboard - Backport #39958: mimic: mgr/dashboard: Resolve TestBed performance issueRejectedActions
Actions #1

Updated by Anonymous almost 5 years ago

  • Pull request ID set to 21783
Actions #2

Updated by Anonymous almost 5 years ago

  • Subject changed from mgr/dashboard: to mgr/dashboard: Resolve TestBed performance issue
Actions #3

Updated by Anonymous almost 5 years ago

  • Copied to Backport #39958: mimic: mgr/dashboard: Resolve TestBed performance issue added
Actions #4

Updated by Nathan Cutler almost 5 years ago

  • Assignee set to Stephan Müller
Actions #5

Updated by Nathan Cutler almost 5 years ago

  • Status changed from Pending Backport to Resolved
Actions #6

Updated by Ernesto Puerta almost 3 years ago

  • Project changed from mgr to Dashboard
Actions

Also available in: Atom PDF