This worklog has been replaced with mariadb.org/jira

This site is here for historical purposes only. Do not add or edit tasks here!

 
 
 

WorkLog Frontpage Log in / Register
High-Level Description | Task Dependencies | High-Level Specification | Low-Level Design | File Attachments | User Comments | Time Estimates | Funding and Votes | Progress Reports

 client-side compressed types
Title
Task ID240
Queue
Version
Status
Priority
Copies toSergei

Created byMdcallag30 Sep 2011Done
Supervisor   
Lead Architect    
Architecture Review  
Implementor  
Code Review  
QA  
Documentation  
 High-Level Description
Is it possible to add a variant of the blob types that is compressed on the client 
side? By this I mean that the client library handles compression and decompression 
so that the client code does not have to deal with it. 

The benefit from this is reduced load. There will be less network traffic between 
client/server and master/slave. This uses less space in the binlog, relay log, 
innodb transaction log and database files. The alternative is to use compression 
between client/server and master/slave but that doesn't help with the size of the 
binlog file nor with the innodb datafiles or log file.

We have too many cases where huge text/blob values store uncompressed JSON and the 
bloat from that hurts performance.
 Task Dependencies
Others waiting for Task 240Task 240 is waiting forGraph
 
 High-Level Specification
 Low-Level Design
 File Attachments
 NameTypeSizeByDate
 User Comments
 Time Estimates
NameHours WorkedLast Updated
Total0 
 Hrs WorkedProgressCurrentOriginal
Total000
 
 Funding and Votes
Votes: 0: 0%
 Make vote: Useless    Nice to have    Important    Very important    

Funding: 0 offers, total 0 Euro
 Progress Reports
(Sergei - Sat, 01 Oct 2011, 08:48
    
Observers changed: Sergei


Report Generator:
 
Saved Reports:

WorkLog v4.0.0
  © 2010  Sergei Golubchik and Monty Program AB
  © 2004  Andrew Sweger <yDNA@perlocity.org> and Addnorya
  © 2003  Matt Wagner <matt@mysql.com> and MySQL AB