Robert Kaiser Reporter
	Description • 12 years ago

To reduce the amount of data that is transmitted in a crash report submission, we should (be able to) compress it with gzip. This is interesting mainly for mobile devices on a data plan, but also might help in general for people on slow connections by making submission faster.

Ted tried compressing a B2G crash dump with gzip, and it seems to have a significnat effect:

<ted>   -rw-r--r-- 1 luser luser 72824 Aug  9 08:52 562b891f-4a47-9653-61a7bca1-6871d8b9.dmp
<ted>   -rw-r--r-- 1 luser luser 14387 Aug  9 08:52 562b891f-4a47-9653-61a7bca1-6871d8b9.dmp.gz
<ted>   so yeah...
<ted>   we could take that 72k down to 14k with just gzip


I guess we'd need support both on the Breakpad side to send them compressed, and on the Socorro side to decompress them on the server (if in the collector or processor might also be a valid question there, but I leave that up to people there).

	Justin Dolske [:Dolske]
	Comment 1 • 12 years ago

A hopefully-easy alternative would be to see if the crash submitter stack is able to use gzip encoding when transferring?

	(not currently active) Ted Mielczarek
	Comment 2 • 12 years ago

That's tricky, since we have 5 different crash submitter stacks. Every platform uses native libraries to submit, except B2G uses CrashSubmit.jsm (which OOP plugin crashes use, as well as about:crashes when you click to submit).

	Robert Kaiser Reporter
	Comment 3 • 12 years ago

OK, so we should split this into separate bugs for every platform. I will file ones for Android and B2G/CrashSubmit.jsm first, once we have testing on the server side working, we can file bugs for the other platforms as well.