# Epic OP-7251 - Speed up initial load time of wp table

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-7251

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

### User Problem

#### User

*Users with access to more than ca 30-50 work packages among which are:*

  - Project manager
  - Project member
  - Product owner

#### Problem

The initial loading of the work package table can be quite slow especially if a large page size is selected. The large page size is typically selected by users who want to plan and/or get an overview.

#### Pain

  - Wait
  - Decrease page size which limits the value of the view

### Business Case

#### Confidence

  - Slow backend
  - Overhead of transporting data from backend to frontend

#### Urgency and Priority

We get a lot of complaints regarding the poor performance

### Solution

We currently load data for the whole pageSize. So if a user chooses to display 300 work packages per page we load 300 work package from the backend. But we can only, and thus only need to, display a much lower number on the screen when the page loads. Therefore, we can:

  - Load only as many work packages as can fit the screen, regardless of the page size the user selected.
  - Render the table for the subset,
  - Load the rest (or all) of the actually desired page without the user noticing.
  - Render the whole of the table.

#### Out of Scope for the MVC

  - Remove page size in favor of infinite/virtual scrolling.
  - Speed up backend
  - Speed up table rendering

#### Differentiation

  - A pleasant working experience without being interrupted by wait time

#### Next iteration

  - Increase Backend-Performance (JSON in DB, signaling)
  - infinite/virtual scrolling

### Launch and Growth

#### Measures

  - No more complaints about poor performance on initial page load

#### Messaging

*If you were to write a press release, how would you describe the value to customers?*

<figure class="table"><table><tbody><tr><th>Headline</th><td>OpenProject now twice as fast</td></tr><tr><th>First Paragraph</th><td>The work package view in OpenProject now loads significantly faster. This makes working in OpenProject a breeze.</td></tr><tr><th>Customer Quote</th><td>"OpenProject is snappy and fast. I can directly create my project plan in OpenProject without having to rely on MS Project."</td></tr></tbody></table></figure>

#### Go to market

*How are you planning on getting this into users' hands?*
