#6 no data loaded (cont'd)

parser (12)
Mike Medved

This is a continuation of the previous issue since it was closed out. I tested out beta3 and got better results, but still had some problems. From my original post, output and output 3 (both contain AM | PM) do not load in kSar. I tried loading in the format that detects AM | PM and the regular format to no avail. It does look like it got the date range correct this time.

For the one file that did get loaded correctly (output2), the used graph looks off to me. I looked through the file and there are various spots where the CPU says it is 0% for a paricular category (sys, for example) but the chart doesn't seem to indicate this. See attached jpeg and table below.

08:50:58 CPU %usr %nice %sys %iowait %steal %irq %soft %guest %idle
08:50:59 all 9.71 0.00 2.43 0.00 0.00 0.00 0.00 0.00 87.86
08:50:59 0 1.96 0.00 2.94 0.00 0.00 0.00 0.00 0.00 95.10
08:50:59 1 16.35 0.00 1.92 0.00 0.00 0.00 0.00 0.00 81.73

Am I reading the chart wrong?

Thanks for all your hard work!



  • Mike Medved

    Mike Medved - 2010-09-13
  • Mike Medved

    Mike Medved - 2010-09-13
  • Mike Medved

    Mike Medved - 2010-09-13
  • Mike Medved

    Mike Medved - 2010-09-13
  • Alexandre Cherif


    Great one, i've add the column index on the graph instead of column value

    thanks for you report

  • Alexandre Cherif

    • labels: --> parser
    • priority: 5 --> 9
    • assigned_to: nobody --> xcherif
    • status: open --> pending-fixed
  • Mike Medved

    Mike Medved - 2010-09-13

    Confirmed... beta4 fixes the graph problem.

    Another data point for you on the other two files... if I load output2 and then do a new window I can load output.txt and it appears to load correctly. If I try the same trick with output3, no dice.

  • Alexandre Cherif


    the fix to you problem has been released, if you got some time to test it


  • Alexandre Cherif

    • status: pending-fixed --> closed-fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks