Changes between Initial Version and Version 3 of Ticket #2086


Ignore:
Timestamp:
May 16, 2009, 3:44:19 PM (13 years ago)
Author:
charles
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2086

    • Property Owner set to charles
    • Property Status changed from new to assigned
    • Property Summary changed from JSON RPC messages should use less bandwidth and CPU to JSON RPC messages can be 84% shorter, saving bandwidth and CPU
    • Property Milestone changed from None Set to 1.62
  • Ticket #2086 – Description

    initial v3  
    11libtransmission's JSON/RPC messages use a lot more space than they need to.  This wastes bandwidth and CPU cycles for deflate().
    22
    3   1. By far the biggest waste is whitespace added to make the JSON human-readable.
     3  1. The biggest waste is whitespace added to make the JSON human-readable.  Our JSON config files need to be human-readable, but the the RPC messages don't.
    44  2. Floating point numbers are being sent through with more decimal places than any of our clients need
    55  3. As a special case, "0.00000000" happens very frequently.  We should test for this and send the result as "0" instead.
     
    1313
    1414Final result: '''84% SHORTER'''
    15 
    16 These optimizations should be optional: we want to keep the config files human-readable.
    17 
    18 Marking the component as "Transmission", rather than "libtransmission", since the qt, gtk, and transmission-remote clients all use the JSON generator.