Skip to content

Optimize factory creation in user view issues spec

Aishwarya Subramanian requested to merge optimize_user_views_issue_spec into master

What does this MR do?

This MR improvises the user view issues spec by reducing the number of database objects created. It's listed in one of the top 10 time consuming specs.

The performance analysis and inference is as listed below:

Before:

[TEST PROF INFO] EventProf results for sql.active_record

Total time: 00:03.759 of 01:00.983 (6.16%)
Total events: 1903

Top 5 slowest suites (by time):

User views issue (./spec/features/issues/user_views_issue_spec.rb:5) – 00:03.759 (1903 / 6) of 01:00.983 (6.16%)

Flame Graph:

Screen_Shot_2020-08-26_at_11.56.33_AM

After:

[TEST PROF INFO] EventProf results for sql.active_record

Total time: 00:02.068 of 00:54.063 (3.83%)
Total events: 1164

Top 5 slowest suites (by time):

User views issue (./spec/features/issues/user_views_issue_spec.rb:5) – 00:02.068 (1164 / 6) of 00:54.063 (3.83%)

Flame Graph:

Screen_Shot_2020-08-26_at_12.01.56_PM

Inferences:

  1. Number of database queries decreased from 1903 to 1164
  2. Top-level create stacks reduced from 31 to 11
  3. Total time was reduced by 37.82%

Queries saved: 793

Mentions gitlab-com/www-gitlab-com#8851 (closed)

Screenshots

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by John Hope

Merge request reports