View Single Post
  #190  
Old Today, 05:22
kj911 kj911 is offline
Registered User
 
Join Date: Apr 2010
Location: world
Posts: 252
Thanks: 166
Thanked 95 Times in 67 Posts
kj911 is on a distinguished road
Nitro NG 1.05 [FAST ZLIB PRECOMPRESOR] [OPEN SOURCE]

Very shorted descriptions:
Code:
================================================================================
          NITRO ENGINE - ARCHITECTURAL CHANGELOG: v1.03 -> v1.05 HP
================================================================================

[SUMMARY]
* v1.03 Baseline: Single-pass linear engine. Isolated from Preflate bugs.
                  Used precise 1-to-1 scanning but lacked memory recycling.
* v1.05 HP:       Hardware-aware system featuring Zlib stream memorization,
                  lock-free lookups, real-time pipeline streaming, thread
                  memory pools, and purist native Win32/POSIX E/S interfaces.
Longer descriptions and x64 Win/Linux binaries here.

My test, detects huge memory footprints, larger than previously posted "precomp_zlib" iterations. Original precomp 0.4.8 still have 24-40MB RAM usage during compress/recompress from testing 124MB ARC archive. Precomp_zlib around ~200MB, NitroNG memory spikes avg. 500MB RAM!

Bad memory mapping code?

My 32bit (XP-compatible) EXE's patched in 4GB RAM limit, avg. 2720-2725MB's memory allocated in 64bit host, before crashing. Speed comparable to Precomp_Zlib iterations. Multithreaded.
Attached Files
File Type: 7z nitro_ng_v1_05_x86.7z (995.2 KB, 5 views)

Last edited by kj911; Today at 05:25. Reason: typo fix
Reply With Quote