1864944 - Investigate the performance cost of re-opening a connection on each sync.

Status: NEW

(Application Services :: Sync, enhancement, P3)

Description

[Mark Hammond [:markh] [:mhammond]]

From github: https://github.com/mozilla/application-services/issues/952.

Initializing the sync connection is not free (although maybe it is cheap enough that it does not matter?), and as of #948 we do so at the start of every places sync.

This bug is to measure the cost, and determine if it's worth the effort to keep it around across syncs.

Note: For future reference, the reasons we resolved #948 the way we did were:

• To avoid having a function we need to remember to update if temp tables are used.
• @linacambridge and @mhammond were both surprised that the connection lived past the end of the sync, and it seemed less error-prone to move the code to behave that way, than to audit all the cases where an assumption opposite to that may have been made.
• To avoid bugs where we accidentally ran triggers in some new 'clear things before sync' function because they DELETEd something from a table instead of dropping it.

┆Issue is synchronized with this Jira Task
┆Epic: Sync Ecosystem (backlog)

Change performed by the Move to Bugzilla add-on.