Results 1 to 16 of 16

Thread: TC 5.0dev2 released!

  1. #1
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    What's new:
    + Improved literal/match length coding
    + Optimized and minimized source code
    + Simplified decoder

    Download TC 5.0dev2 (23 KB)


  2. #2
    Member
    Join Date
    May 2006
    Location
    Uruguay
    Posts
    30
    Thanks
    0
    Thanked 1 Time in 1 Post
    <u>sharks12.txt</u> 5.582.655 bytes
    TC 5.0dev2 e Process Time = 2.015 - 1.851.546 bytes
    TC 5.0dev2 d Process Time = 2.218

    <u>gcc-html.tar</u> 2.754.560 bytes
    TC 5.0dev2 e Process Time = 0.453 - 404.957 bytes
    TC 5.0dev2 d Process Time = 0.500

    <u>TC 5.0dev1 and TC 4.3 Results</u>

  3. #3
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Performance on Large Text Compression Benchmark:

    Layout:
    <compressed size> (<comp. time>/<decomp. time>)

    ENWIK8:
    32,417,139 bytes (25 sec/25 sec)

    ENWIK9:
    283,039,249 bytes (270 sec/244 sec)

    System:
    P4 3.0 GHz, 1 GB RAM, Windows XP Professional SP2


  4. #4
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts

  5. #5
    Guest
    New tc used lzw+ari?

  6. #6
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    No... Look at the map of versions of TC and algorithms used:

    TC 1.0-1.1 - QLZ (My own simple algorithm)
    TC >1.2 - Byte-oriented huffman (My own simple algorithm)
    TC 2.x - PPMCB variant
    TC 3.x - LZC variant
    TC 4.x - LZC variant with large dictionary
    TC 5.x - LZP variant

    Release date of the first version - <u>summer of 2004</u>

  7. #7
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Also note, probably I add this new fast engine to PIMPLE:
    <u>
    Estimated preset map:</u>

    Fastest - Variant of current TC engine
    Normal - Current Fastest preset
    High - Current Normal preset
    Maximum - Current High preset but with Model Order of 5
    Extreme - Maximum preset but with 256 MB Model Size

    Or I can add just support for TC files - and you will able to choose between PIM and TC compression...

  8. #8
    Guest
    Or I can add just support for TC files - and you will able to choose between PIM and TC compression...
    it's better...
    Than differs TC from LZPX?

  9. #9
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Current TC (dev2) is just some kind of simplified and optimized LZPX... Currently I'm experimenting with engine to find what can I do to improve compression, but keeping speed and simplicity.

  10. #10
    Guest
    Also note, probably I add this new fast engine to PIMPLE:

    Estimated preset map:

    Fastest - Variant of current TC engine
    Normal - Current Fastest preset
    High - Current Normal preset
    Maximum - Current High preset but with Model Order of 5
    Extreme - Maximum preset but with 256 MB Model Size


    I like this idea best.

  11. #11
    Guest
    Current TC (dev2) is just some kind of simplified and optimized LZPX... Currently I'm experimenting with engine to find what can I do to improve compression, but keeping speed and simplicity.

    Hi,
    I think you can implement changes similar to LZPXj 1.0a-e. It would improve compression on files containing precompressed data.
    This changes were simple and speed was not affected. If you want I can do this if you send me source.

  12. #12
    Guest
    Hi,
    I think you can implement changes similar to LZPXj 1.0a-e. It would improve compression on files containing precompressed data.
    This changes were simple and speed was not affected. If you want I can do this if you send me source


    This seems like a good idea.

  13. #13
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Currently, I won't add this feature, at least temporarily. Look at the features and phylosophy of this compressor:
    + Developed and maintained only by me
    + As simple as it possible
    + Well structured, optimized and small source code
    + Only the most significant part of the engine will be included - i.e. if some trick improves compression just a little - I won't include this feature
    Currently, I improve the base of the engine - matching portion, index table and literal/match length coding. - To make this parts simple, efficient and well structured.


  14. #14
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Also special thanks to Jan for "simplelzpxj".

  15. #15
    Guest
    Also special thanks to Jan for "simplelzpxj".

    What is this?

  16. #16
    The Founder encode's Avatar
    Join Date
    May 2006
    Location
    Moscow, Russia
    Posts
    4,002
    Thanks
    391
    Thanked 377 Times in 147 Posts
    Also special thanks to Jan for "simplelzpxj".

    What is this?


    It is just improved LZPX 1.5b. (Improved compression on precompressed data)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •