Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce size of Lighthouse payload #21

Open
rviscomi opened this issue Nov 8, 2018 · 4 comments
Open

Reduce size of Lighthouse payload #21

rviscomi opened this issue Nov 8, 2018 · 4 comments
Labels
enhancement New feature or request

Comments

@rviscomi
Copy link
Member

rviscomi commented Nov 8, 2018

The latest lighthouse.2018_10_15 table is 237 GB. Querying all lighthouse tables currently costs 4.15 TB and runs in several minutes.

image

  1. identify parts of the JSON payload that are unnecessary or unlikely to have analytical value and also significant contributors to the payload size
  2. modify the Dataflow pipeline to omit these parts of the payload
  3. profit
@rviscomi rviscomi added the enhancement New feature or request label Nov 8, 2018
@connorjclark
Copy link

Can you point to where this trimming could be done?

@rviscomi
Copy link
Member Author

Hey @connorjclark the get_lighthouse_reports function in the Dataflow pipeline would be the place where we can trim off excess response data

https://github.com/HTTPArchive/bigquery/blob/acef15add27f0ba360fba44e2b74ab2575baed46/dataflow/python/bigquery_import.py#L188-L222

@max-ostapenko max-ostapenko transferred this issue from HTTPArchive/bigquery Oct 18, 2024
@max-ostapenko
Copy link

The lighthouse payload function moved here

@pmeenan
Copy link
Member

pmeenan commented Oct 18, 2024

FWIW, we can also trim the payload directly on the agents which might be cleaner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants