jmforsythe / Git-Heat-Map
- пятница, 3 февраля 2023 г. в 00:36:49
Map showing the cpython repositiory, highlighting the files that Guido van Rossum changed the most
python generate_db.py {path_to_repo_dir}
python flask_app.py
(flask must be installed, can be install from pip)127.0.0.1:5000
This project consists of two parts:
Scans through an entire git history using git log
, and creates a database using three tables:
Using these we can keep track of which files/commits changed the repository the most, which in itself can provide useful insight
Taking the database above, uses an SQL query to generate a JSON object with the following structure:
directory:
"name": <Directory name>
"val": <Sum of sizes of children>
"children": [<directory or file>, ...]
file:
"name": <File name>
"val": <Total number of line changes for this file over all commits>
then uses this to generate an inline svg image representing a treemap of the file system, with the size of each rectangle being the val
described above.
Then generates a second JSON object in a similar manner to above, but filtering for the things we want (only certain emails, date ranges, etc), then uses this to highlight the rectangles in varying intensity based on the val
s returned eg highlighting the files changed most by a certain author.
These speeds were attained on my personal computer.
Repo | Number of commits | Git log time | Git log size | Database time | Database size | Total time |
---|---|---|---|---|---|---|
linux | 1,154,884 | 60 minutes | 444MB | 462.618 seconds | 733MB | 68 minutes |
cpython | 115,874 | 4.6 minutes | 44.6MB | 36.607 seconds | 74.3MB | 5.2 minutes |
Time taken seems to scale linearly, going through approximately 300 commits/second, or requiring 0.0033 seconds/commit. Database size also scales linearly, with approximately 2600 commits/MB, or requiring 384 B/commit.
For this test I filtered each repo by its most prominent authors:
Repo | Author filter | Time taken |
---|---|---|
linux | torvalds@linux-foundation.org | 45.4 seconds |
cpython | guido@python.org | 1.9 seconds |
Currently treemap.js
uses a global variable MIN_AREA
to not render smallest files for better performance.
While these performances are not as fast as desired, a more typically sized repo should perform fine.
Currently the only submodule changes that can be seen are the top level commit pointer changes. In the future would like to recursively explore submodules and add their files to the database.
Currently done using git log which can take a very long time for large repos. Will look into any other ways of getting needed information on files.
Currently no async functions are used. I believe the performance of the webpage could be imporved if things such as file loading and svg drawing was done asynchronously.
Filters must be re-entered every time the page is loaded. Ideally filters would be remembered either through cookies or by storing the filters as a url query, which would allow users to bookmark queries.
Current interface is very barebones. Want to have a sidebar that will allow users to select authors, date ranges, etc, to control the highlighting.
Currently red is hardcoded for all results. In order to show multiple authors we want to highlight in different colours, will need to decide how to colour files edited by both authors.