[Q] Data compression usage topic
Recently, I put together a benchmark for general-purpose lossless data compression algorithms (think zilb and LZMA, not HEVC and MP3). While I was doing so it occurred to me that the standard corpora aren't very representative of the type of data people actually use data compression for these days.
To address this I'm putting together a new corpus and I would like to make sure it includes data relevant for mobile developers. Since I have virtually no experience with mobile development I was hoping some of the developers around here could tell me what kind of data they are compressing (or would like to in the future) so I can include something like it in the corpus, especially the differences from desktop usage.
Note that, in addition to developers using benchmarks run against this data to help decide what codec(s) to consider for their project, the data from this corpus will also be used by people writing compression codecs to help tune their algorithms and implementations—in other words, if the corpus includes data which is representative of what mobile apps use it will likely result in better compression (higher ratio, faster, lower memory…) for mobile apps.
I can't post links here yet (this is my first post), but for more details see the project page at <https://github.com/nemequ/squash-corpus>. There is an item in the issue tracker for "Data from a mobile app", but it's pretty vague—that's what I'm here trying to pin down, especially content that doesn't really fit into one of the other issues.
To address this I'm putting together a new corpus and I would like to make sure it includes data relevant for mobile developers. Since I have virtually no experience with mobile development I was hoping some of the developers around here could tell me what kind of data they are compressing (or would like to in the future) so I can include something like it in the corpus, especially the differences from desktop usage.
Note that, in addition to developers using benchmarks run against this data to help decide what codec(s) to consider for their project, the data from this corpus will also be used by people writing compression codecs to help tune their algorithms and implementations—in other words, if the corpus includes data which is representative of what mobile apps use it will likely result in better compression (higher ratio, faster, lower memory…) for mobile apps.
I can't post links here yet (this is my first post), but for more details see the project page at <https://github.com/nemequ/squash-corpus>. There is an item in the issue tracker for "Data from a mobile app", but it's pretty vague—that's what I'm here trying to pin down, especially content that doesn't really fit into one of the other issues.
xda-developers
- Sprint Nexus 6 no mobile data on CM 12.1. topic
- [Q] Data from both sim cards? topic
- Simultaneous Voice and Data on Tmobile with VS980 topic
- [Q] Remove the carrier modified data icons? topic
- Backup data in Private Mode topic
- [Q] Lost Data !! topic
- [q] lollipop data connection issues topic
- Data issue topic
- Is root required to roll back to KitKat? topic
- [REQ] Multi DPI Stock Camera topic
- May be this is it for Xperia J topic
- [Q] No IMEI and baseband anymore. So back to stock rom for repair! topic
- [Q] New to phone - on 24A rooted - where to go from here? topic
- Htc desire 816 official lollipop update video review topic
- [Q] Galaxy S6 Edge T-Mobile Unlock by SIM code topic
- How to roll back to KK topic
- What is this in Greenify settings topic
- [Q] How to update? topic
- [Q] Ram usage on kitkat vs lollipop topic
- Battery Usage topic
0 commentaires:
Enregistrer un commentaire