| Hi agner.org/optimize/ Thank you for this tool. Tiny problem: I noticed that disassembly of large files takes suspiciously long (all PE EXE): CRC32.EXE 77'824 Byte's 0.9 s Test
OCC.EXE 446'976 Byte's 47 s Test
MPWRC4.EXE 17'455'616 Byte's 230 Ks AKA 2.7 days Prediction The time grows with file size, but not linearly, not even quadratically, but with an exponent of 2.3. So on bigger files it simply seems to hang. There is a FAQ on this subject, but it doesn't reveal too much. 2 suggestions: - Enhance the FAQ (about the exponent of 2.3), also about memory requirements (do they also grow that way ?) - Would it be possible to add some progress indicator ? Telling how much has been done at suitable times (for example 3s, 12s, 1m, 6m, 1h, 4h, 24h, 4 days) ? Disassembling MPLAYER would take almost 3 days, so it would be cool to know that the work is doing some progress rather than hanging really and permanently. | 
Objconv - disassembly performance & P.I. - dos386 - 2011-03-05
Objconv - disassembly performance & P.I. - Agner - 2011-03-05