Page MenuHomeSoftware Heritage

Write all new objects to azure synchronously
Closed, MigratedEdits Locked


To fill the Rocquencourt / Azure gap, we need to make sure all new objects are written to azure synchronously.

The previous experimentation of this setup failed because the performance hit was gigantic. We've decided to

  • deploy the multiplexing object storage backend
  • investigate (and mitigate) the multiplexing performance issues (by deploying the statsd probes that are currently WIP, and tracing the actual behavior of the code)