Revision f78c76f5b796c1b0f3ed4a1aeed0fb28200e0ff6 authored by Valentin Lorentz on 12 August 2020, 14:21:01 UTC, committed by Valentin Lorentz on 14 August 2020, 14:35:08 UTC
1 parent 6651130
archive-copies.rst
:orphan:
.. _archive-copies:
Archive copies
==============
.. _swh-storage-copies-layout:
.. figure:: images/swh-archive-copies.svg
:width: 1024px
:align: center
Layout of Software Heritage archive copies (click to zoom).
The Software Heritage archive exists in several copies, to minimize the risk of
losing archived source code artifacts. The layout of existing copies, their
relationships, as well as their geographical and administrative domains are
shown in the layout diagram above.
We recall that the archive is conceptually organized as a graph, and
specifically a Merkle DAG, see :ref:`data model <data-model>` for more
information.
Ingested source code artifacts land directly on the **primary copy**, which is
updated live and also used as reference for deduplication purposes. There,
different parts of the Merkle DAG as stored using different backend
technologies. The leaves of the graph, i.e., *content objects* (or "blobs"),
are stored in a key-value object storage, using their SHA1 identifiers as keys
(see :ref:`persistent identifiers <persistent-identifiers>`). SHA1 collision
avoidance is enforced by the :mod:`swh.storage` module. The *rest of the graph*
is stored in a Postgres database (see :ref:`SQL storage <sql-storage>`).
At the time of writing, the primary object storage contains about 5 billion
blobs with a median size of 3 KB---yes, that is *a lot of very small
files*---for a total compressed size of about 200 TB. The Postgres database
takes about 8 TB, half of which required by indexes. In terms of graph metrics,
the Merkle DAG has about 10 B nodes and 100 B edges.
The **secondary copy** is hosted on Microsoft Azure cloud, using its native
blob storage for the object storage and a large virtual machine to run a
Postgres instance there. The database is kept up-to-date w.r.t. the primary
copy using Postgres WAL replication. The object storage is kept up-to-date
using :mod:`swh.archiver`.
Archive copies (as opposed to archive mirrors) are operated by the Software
Heritage Team at Inria. The primary archived copy is geographically located at
Rocquencourt, France; the secondary copy hosted in the Europe West region of
the Azure cloud.
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...