[asterisk-users] Free Fax for Asterisk -- benchfax utility hangs.

Tue Jul 21 17:46:00 CDT 2009

Kevin P. Fleming wrote:

> You say it has stopped at different points as you've run different
> tests; can you verify that? If it always stops at 'nocona', that would
> mean one particular type of problem, but if it stops at various
> different places, then that would point to something very different.

Hello Kevin.

Thanks for the reply.

I have three examples that follow.   The first I ended after 11 minutes.
I got as far as nocona, then the hang.

The next run had me down to c3 in 8 minutes, before hanging there.  I
let it run for another 8 minutes or so.

Finally, I let the thing run for 24 minutes and only got to nocona again.

What is a reasonable time for this entire test suite to finish, if it
completed normally?

Barry

 [root at corp-asterisk ~]# time ./benchfax
benchfax version 1.0.7

Use the '-l' option to see license information for software
included in this program.

Running test using CCITT FAX test page, US letter size, 204x196
resolution, MMR encoding, ECM enabled and V.17 (14.4kbps) modem

NOTE: Each individual test could take 20 seconds or longer; be patient.
Test run 1 for flavor 'i686' used 658 milliseconds of CPU time.
Test run 2 for flavor 'i686' used 632 milliseconds of CPU time.
Test run 3 for flavor 'i686' used 413 milliseconds of CPU time.
Test run 4 for flavor 'i686' used 188 milliseconds of CPU time.
Test run 5 for flavor 'i686' used 202 milliseconds of CPU time.
Test run 1 for flavor 'pentium3m' used 633 milliseconds of CPU time.
Test run 2 for flavor 'pentium3m' used 636 milliseconds of CPU time.
Test run 3 for flavor 'pentium3m' used 651 milliseconds of CPU time.
Test run 4 for flavor 'pentium3m' used 676 milliseconds of CPU time.
Test run 5 for flavor 'pentium3m' used 645 milliseconds of CPU time.
Test run 1 for flavor 'pentium-m' used 632 milliseconds of CPU time.
Test run 2 for flavor 'pentium-m' used 639 milliseconds of CPU time.
Test run 3 for flavor 'pentium-m' used 187 milliseconds of CPU time.
Test run 4 for flavor 'pentium-m' used 481 milliseconds of CPU time.
Test run 5 for flavor 'pentium-m' used 644 milliseconds of CPU time.
Test run 1 for flavor 'pentium4m' used 183 milliseconds of CPU time.
Test run 2 for flavor 'pentium4m' used 676 milliseconds of CPU time.
Test run 3 for flavor 'pentium4m' used 654 milliseconds of CPU time.
Test run 4 for flavor 'pentium4m' used 689 milliseconds of CPU time.
Test run 5 for flavor 'pentium4m' used 611 milliseconds of CPU time.
Test run 1 for flavor 'prescott' used 670 milliseconds of CPU time.
Test run 2 for flavor 'prescott' used 340 milliseconds of CPU time.
Test run 3 for flavor 'prescott' used 484 milliseconds of CPU time.
Test run 4 for flavor 'prescott' used 701 milliseconds of CPU time.
Test run 5 for flavor 'prescott' used 662 milliseconds of CPU time.
Beginning cache-load run for flavor 'nocona'...

real    11m29.829s
user    0m16.895s
sys     0m3.393s
[root at corp-asterisk ~]#

[root at corp-asterisk ~]# time ./benchfax
benchfax version 1.0.7

Use the '-l' option to see license information for software
included in this program.

Running test using CCITT FAX test page, US letter size, 204x196
resolution, MMR encoding, ECM enabled and V.17 (14.4kbps) modem

NOTE: Each individual test could take 20 seconds or longer; be patient.
Test run 1 for flavor 'i686' used 648 milliseconds of CPU time.
Test run 2 for flavor 'i686' used 680 milliseconds of CPU time.
Test run 3 for flavor 'i686' used 674 milliseconds of CPU time.
Test run 4 for flavor 'i686' used 625 milliseconds of CPU time.
Test run 5 for flavor 'i686' used 633 milliseconds of CPU time.
Test run 1 for flavor 'pentium3m' used 634 milliseconds of CPU time.
Test run 2 for flavor 'pentium3m' used 640 milliseconds of CPU time.
Test run 3 for flavor 'pentium3m' used 634 milliseconds of CPU time.
Test run 4 for flavor 'pentium3m' used 636 milliseconds of CPU time.
Test run 5 for flavor 'pentium3m' used 647 milliseconds of CPU time.
Test run 1 for flavor 'pentium-m' used 623 milliseconds of CPU time.
Test run 2 for flavor 'pentium-m' used 616 milliseconds of CPU time.
Test run 3 for flavor 'pentium-m' used 626 milliseconds of CPU time.
Test run 4 for flavor 'pentium-m' used 679 milliseconds of CPU time.
Test run 5 for flavor 'pentium-m' used 668 milliseconds of CPU time.
Test run 1 for flavor 'pentium4m' used 448 milliseconds of CPU time.
Test run 2 for flavor 'pentium4m' used 669 milliseconds of CPU time.
Test run 3 for flavor 'pentium4m' used 631 milliseconds of CPU time.
Test run 4 for flavor 'pentium4m' used 645 milliseconds of CPU time.
Test run 5 for flavor 'pentium4m' used 652 milliseconds of CPU time.
Test run 1 for flavor 'prescott' used 683 milliseconds of CPU time.
Test run 2 for flavor 'prescott' used 658 milliseconds of CPU time.
Test run 3 for flavor 'prescott' used 662 milliseconds of CPU time.
Test run 4 for flavor 'prescott' used 662 milliseconds of CPU time.
Test run 5 for flavor 'prescott' used 660 milliseconds of CPU time.
Test run 1 for flavor 'nocona' used 650 milliseconds of CPU time.
Test run 2 for flavor 'nocona' used 660 milliseconds of CPU time.
Test run 3 for flavor 'nocona' used 680 milliseconds of CPU time.
Test run 4 for flavor 'nocona' used 670 milliseconds of CPU time.
Test run 5 for flavor 'nocona' used 666 milliseconds of CPU time.
Test run 1 for flavor 'core2' used 659 milliseconds of CPU time.
Test run 2 for flavor 'core2' used 640 milliseconds of CPU time.
Test run 3 for flavor 'core2' used 636 milliseconds of CPU time.
Test run 4 for flavor 'core2' used 243 milliseconds of CPU time.
Test run 5 for flavor 'core2' used 630 milliseconds of CPU time.
Flavor 'k6-3' failed, skipping.avor 'k6-3'...
Test run 1 for flavor 'athlon' used 658 milliseconds of CPU time.
Test run 2 for flavor 'athlon' used 628 milliseconds of CPU time.
Test run 3 for flavor 'athlon' used 679 milliseconds of CPU time.
Test run 4 for flavor 'athlon' used 638 milliseconds of CPU time.
Test run 5 for flavor 'athlon' used 636 milliseconds of CPU time.
Test run 1 for flavor 'athlon-xp' used 652 milliseconds of CPU time.
Test run 2 for flavor 'athlon-xp' used 227 milliseconds of CPU time.
Test run 3 for flavor 'athlon-xp' used 649 milliseconds of CPU time.
Test run 4 for flavor 'athlon-xp' used 645 milliseconds of CPU time.
Test run 5 for flavor 'athlon-xp' used 661 milliseconds of CPU time.
Test run 1 for flavor 'opteron' used 669 milliseconds of CPU time.
Test run 2 for flavor 'opteron' used 228 milliseconds of CPU time.
Test run 3 for flavor 'opteron' used 551 milliseconds of CPU time.
Test run 4 for flavor 'opteron' used 675 milliseconds of CPU time.
Test run 5 for flavor 'opteron' used 656 milliseconds of CPU time.
Test run 1 for flavor 'opteron-sse3' used 646 milliseconds of CPU time.
Test run 2 for flavor 'opteron-sse3' used 685 milliseconds of CPU time.
Test run 3 for flavor 'opteron-sse3' used 667 milliseconds of CPU time.
Test run 4 for flavor 'opteron-sse3' used 666 milliseconds of CPU time.
Test run 5 for flavor 'opteron-sse3' used 191 milliseconds of CPU time.
Test run 1 for flavor 'barcelona' used 645 milliseconds of CPU time.
Test run 2 for flavor 'barcelona' used 691 milliseconds of CPU time.
Test run 3 for flavor 'barcelona' used 613 milliseconds of CPU time.
Test run 4 for flavor 'barcelona' used 660 milliseconds of CPU time.
Test run 5 for flavor 'barcelona' used 642 milliseconds of CPU time.
Beginning cache-load run for flavor 'c3'...

real    16m0.536s
user    0m44.425s
sys     0m5.019s

[root at corp-asterisk ~]# time ./benchfax
benchfax version 1.0.7

Use the '-l' option to see license information for software
included in this program.

Running test using CCITT FAX test page, US letter size, 204x196
resolution, MMR encoding, ECM enabled and V.17 (14.4kbps) modem

NOTE: Each individual test could take 20 seconds or longer; be patient.
Test run 1 for flavor 'i686' used 639 milliseconds of CPU time.
Test run 2 for flavor 'i686' used 662 milliseconds of CPU time.
Test run 3 for flavor 'i686' used 665 milliseconds of CPU time.
Test run 4 for flavor 'i686' used 635 milliseconds of CPU time.
Test run 5 for flavor 'i686' used 642 milliseconds of CPU time.
Test run 1 for flavor 'pentium3m' used 648 milliseconds of CPU time.
Test run 2 for flavor 'pentium3m' used 627 milliseconds of CPU time.
Test run 3 for flavor 'pentium3m' used 670 milliseconds of CPU time.
Test run 4 for flavor 'pentium3m' used 649 milliseconds of CPU time.
Test run 5 for flavor 'pentium3m' used 628 milliseconds of CPU time.
Test run 1 for flavor 'pentium-m' used 620 milliseconds of CPU time.
Test run 2 for flavor 'pentium-m' used 632 milliseconds of CPU time.
Test run 3 for flavor 'pentium-m' used 659 milliseconds of CPU time.
Test run 4 for flavor 'pentium-m' used 220 milliseconds of CPU time.
Test run 5 for flavor 'pentium-m' used 399 milliseconds of CPU time.
Test run 1 for flavor 'pentium4m' used 649 milliseconds of CPU time.
Test run 2 for flavor 'pentium4m' used 561 milliseconds of CPU time.
Test run 3 for flavor 'pentium4m' used 630 milliseconds of CPU time.
Test run 4 for flavor 'pentium4m' used 643 milliseconds of CPU time.
Test run 5 for flavor 'pentium4m' used 632 milliseconds of CPU time.
Test run 1 for flavor 'prescott' used 680 milliseconds of CPU time.
Test run 2 for flavor 'prescott' used 660 milliseconds of CPU time.
Test run 3 for flavor 'prescott' used 698 milliseconds of CPU time.
Test run 4 for flavor 'prescott' used 236 milliseconds of CPU time.
Test run 5 for flavor 'prescott' used 673 milliseconds of CPU time.
Beginning cache-load run for flavor 'nocona'...

real    24m20.434s
user    0m18.397s
sys     0m2.056s