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

From Software Heritage Wiki
Jump to navigation Jump to search
(Add 'what was done' section)
(Add 'highlights' section)
Line 1: Line 1:
 
* '''Title:''' Graph compression
 
* '''Title:''' Graph compression
 +
 
* '''Description:''' The Software Heritage [https://docs.softwareheritage.org/devel/swh-model/data-model.html data model] is a big [https://en.wikipedia.org/wiki/Merkle_tree Merkle] DAG made of nodes like revisions, releases, directories, etc. It is a very big graph, with 12 billion nodes and 165 billion 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.
 
* '''Description:''' The Software Heritage [https://docs.softwareheritage.org/devel/swh-model/data-model.html data model] is a big [https://en.wikipedia.org/wiki/Merkle_tree Merkle] DAG made of nodes like revisions, releases, directories, etc. It is a very big graph, with 12 billion nodes and 165 billion 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 'haltode' Allançon
 
* '''Student:''' Thibault 'haltode' Allançon
 
** [https://forge.softwareheritage.org/p/haltode/ forge activity]
 
** [https://forge.softwareheritage.org/p/haltode/ forge activity]
 
** [https://summerofcode.withgoogle.com/projects/#4670175868092416 project on the GSoC portal]
 
** [https://summerofcode.withgoogle.com/projects/#4670175868092416 project on the GSoC portal]
 +
 
* '''What was done:'''
 
* '''What was done:'''
 
** Git repo: [https://forge.softwareheritage.org/source/swh-graph/ swh-graph] (list of my [https://forge.softwareheritage.org/people/commits/257/ commits])
 
** Git repo: [https://forge.softwareheritage.org/source/swh-graph/ swh-graph] (list of my [https://forge.softwareheritage.org/people/commits/257/ commits])
Line 13: Line 16:
 
** Automated benchmarking tools with statistical analysis
 
** Automated benchmarking tools with statistical analysis
 
** General documentation on docker environment, compression steps, graph query use-cases, etc.
 
** General documentation on docker environment, compression steps, graph query use-cases, etc.
 +
 +
* '''Highlights:'''
 +
** Compression rates: 4.48 bits/edge (transposed graph) and 4.91 bits/edge (direct graph)
 +
** Memory requirements for loading both graphs: 200GB of RAM
 +
** Total compression time: 1 week
 +
** Node successors lookup times: below 2μs
 +
 
* '''Mentors:'''
 
* '''Mentors:'''
 
** [[User:StefanoZacchiroli|Stefano Zacchiroli]]
 
** [[User:StefanoZacchiroli|Stefano Zacchiroli]]
 
** Antoine Pietri
 
** Antoine Pietri
 +
 
* '''Activity reports:'''
 
* '''Activity reports:'''
 
** [https://haltode.fr/gsoc2019/march.html March 2019]
 
** [https://haltode.fr/gsoc2019/march.html March 2019]

Revision as of 12:01, 22 August 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 12 billion nodes and 165 billion 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.
  • What was done:
    • Git repo: swh-graph (list of my commits)
    • Research on graph compression: evaluate/experiment feasibility and compression rate of multiple techniques
    • Docker environment and scripts to automate the entire compression pipeline
    • REST API to query the graph
      • Java server side: load the compressed graph, run API endpoints traversal algorithms, unit tests, javadoc
      • Python client side: integration with SWH infrastructure, integration tests
    • Automated benchmarking tools with statistical analysis
    • General documentation on docker environment, compression steps, graph query use-cases, etc.
  • Highlights:
    • Compression rates: 4.48 bits/edge (transposed graph) and 4.91 bits/edge (direct graph)
    • Memory requirements for loading both graphs: 200GB of RAM
    • Total compression time: 1 week
    • Node successors lookup times: below 2μs
Retrieved from "https://wiki.softwareheritage.org/index.php?title=Google_Summer_of_Code_2019/Graph_compression&oldid=1097"