Page MenuHomeSoftware Heritage

Investigate why reading the journal of the content table takes so long
Closed, ResolvedPublic

Description

When running the last dataset export, the directory table was read from the journal reasonably fast, but the content table had a gigantic ETA. This is especially strange because the content exporter does almost nothing (single write per node).

We should find out if that always happens, even with a dummy exporter that does nothing. If it does, then it's likely a problem in the journal.

Event Timeline

seirl triaged this task as Normal priority.Feb 2 2021, 2:00 PM
seirl created this task.
seirl closed this task as Resolved.EditedApr 27 2022, 10:12 AM

No longer happens with a more recent stack