Opened 7 years ago

Closed 2 years ago

#7744 closed defect (wontfix)

Make output smaller by removing comments and unnecessary data

Reported by: grarpamp Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Compass Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Can someone remove this comment from the compass output.
It will save 120kB per full query, which via Tor is no small amount.

<!-- it's not a fingerprint -->

Child Tickets

Attachments (1)

compass-json-request.txt (5.9 KB) - added by karsten 7 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 7 years ago by grarpamp

Also remove the empty newlins and spaces surrounding the atlas details links. That's another wasted 53kB.

comment:2 Changed 7 years ago by arma

Shouldn't these bytes be sent compressed to the browser?

comment:3 Changed 7 years ago by grarpamp

Only if the 'browser' supports compression.

There's also this errant embedded space...
title=" Probability

And about 21kB worth of 6 spaces plus nl between each <tr> that might as well go.
That's about as tight as it could reasonably get. So about 190kB total.

comment:4 Changed 7 years ago by grarpamp

In the json version the as_no, as_info, and as_name fields are redundant amongst themselves.
Dropping as_info and joining as_no and as_name where needed for display could save about 132kB.

comment:5 in reply to:  4 Changed 7 years ago by karsten

Replying to grarpamp:

In the json version the as_no, as_info, and as_name fields are redundant amongst themselves.
Dropping as_info and joining as_no and as_name where needed for display could save about 132kB.

Interesting! The JSON version is what was introduced by the angularize stuff, I guess? How would I look into the JSON data when making a request?

comment:6 Changed 7 years ago by grarpamp

I don't know JS/angularize, I presume the data fields are used by the other JS code the browser downloads in order to display them. If you mean how to see https transactions you can use 'tamper data' plugin with Firefox. Fetch urls offline with curl or equivalent. result.json with arguments provides the raw tor data for scrapers.

Changed 7 years ago by karsten

Attachment: compass-json-request.txt added

comment:7 Changed 7 years ago by karsten

Agreed, as_info and as_no + as_name are redundant. I attached a sample JSON request.

comment:8 Changed 2 years ago by karsten

Severity: Normal
Summary: compass: trim out the fatMake output smaller by removing comments and unnecessary data

Attempt to make the summary more meaningful.

comment:9 Changed 2 years ago by karsten

Owner: changed from gsathya to metrics-team
Status: newassigned

I believe that gsathya has stopped working on any of these tickets quite a while ago. Reassigning to the friendly metrics-team user. (gsathya, thanks for having worked on all these tickets back when you did!)

comment:10 Changed 2 years ago by irl

Resolution: wontfix
Status: assignedclosed

The metrics team has put a goal of shutting down Compass in its roadmap and merging functionality with Relay Search (previously known as Atlas). This ticket is specific to Compass and as development on Compass has ceased, I am marking this ticket as wontfix.

See #23517 for information on the planned work to integrate Compass functionality into Relay Search.

Note: See TracTickets for help on using tickets.