Y26-068 - Bioscan - Investigate reported slowness in the Traction Export process

[andrewsparkes]

Description
As Jamie L representing the lab staff I would like the perceived slowness of the Bioscan export process investigated and if possible improved. The lab staff report it can take up to an hour after clicking the export button for the new Tube and sample to appear in Traction.

Acceptance Criteria
The following outputs from the research are produced:

• Breakdown of time taken for the export process, using realistic sample numbers
• Identify any slow points and if there are possible improvements

Who the primary contacts are for this work
Jamie L

Knowledge or Stake holders
Andrew, Abdullah, Katy

Additional context or information
The process does not take very long when done via the integration suite. Perhaps the volume of samples is an issue.

Process steps as I understand it:

• Click Export button in Limber
• Limber calls Sequencescape api endpoint /api/v2/bioscan/export_pool_xp_to_traction
• This creates a job called ExportPoolXpToTractionJob
• The job creates a compound sample
• And creates a RabbitMQ message to send the compound sample and tube details to Traction
• A Traction consumer picks up the message and the tube and compound sample details are imported into Traction