Objectives

The workflow described bellow is slow in the read and write phase.

We have identified some tracks, but the first objective is to confirm the causes of these slowdowns. The second objective will be to resolve them.

Context

On our platform https://ppan-pprod.opensourcepolitics.net, we use France Connect as identity provider.

Two workflows are tested with JMETER and need to be improved: 

- The write scenario
- The read scenario

Steps to reproduce the write scenario :

1. The user goes to the platform's home page ('https://ppan-pprod.opensourcepolitics.net/')
2. he clicks on the link (button or menu) leading him to the petitions index page,
3. In the search field, enter a few keywords to target the subject petition of the test and then run the search,
4. he clicks on the "find out about the petition and sign it" button of the target petition,
5. He clicks on the "verify your account to sign" button,
6. It is authenticated with FranceConnect (*),
7. He selects his region and signs,
8. He disconnects.

The read scenario : visitor checks out a petition

1. User visits the home page
2. User goes on the initiatives index
3. User visits a petition page

To do

Focus on the scope described by the Jmeter scenario, (Homepage, search, index initiatives, show initiatives, signature initiatives...etc)

READ

• Identify slow read queries
• Identify un-memoized queries
• Identify slow-rendering partials
• Identify n+1 queries

WRITE

This is the part we have the less insights

• Refactor session store initiatives draft creation
• Identify how we can create a petition with as few steps as possible to reduce writing time in the DB
• Identify superfluous entries in the database during the signature phase and delegate as much as possible to Sidekiq
• Improve the performance of the signature counter