Difference between revisions of "Google Summer of Code 2019/Graph compression"

From Software Heritage Wiki
Jump to: navigation, search
(Add weekly recap II)
(Add weekly recap III)
Line 11: Line 11:
 
** [https://sympa.inria.fr/sympa/arc/swh-devel/2019-05/msg00000.html week 2019/19]
 
** [https://sympa.inria.fr/sympa/arc/swh-devel/2019-05/msg00000.html week 2019/19]
 
** [https://sympa.inria.fr/sympa/arc/swh-devel/2019-05/msg00002.html week 2019/20]
 
** [https://sympa.inria.fr/sympa/arc/swh-devel/2019-05/msg00002.html week 2019/20]
 +
** [https://sympa.inria.fr/sympa/arc/swh-devel/2019-05/msg00005.html week 2019/21]
  
 
== Links ==
 
== Links ==

Revision as of 12:44, 24 May 2019

  • Title: Graph compression
  • Description: The Software Heritage data model is a big Merkle DAG made of nodes like revisions, releases, directories, etc. It is a very big graph, with ~17 B nodes and ~160 B edges, which makes it hard to fit in memory using naive approaches. Graph compression techniques have been successfully used to compress the Web graph (which is slightly larger than the Software Heritage one) and make it fit in memory. The goal of this GSoC project is review existing graph compression techniques and apply the most appropriate one to the Software Heritage case, enabling in-memory processing of its Merkle DAG.
  • Student: Thibault Allançon
  • Mentors:
  • Activity reports:

Links