Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 04, 2016, 04:19:33 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: JrDebugLogger - Viewer Speed  (Read 9923 times)

Reldas

  • Charter Member
  • Joined in 2006
  • ***
  • default avatar
  • Posts: 9
    • View Profile
    • Donate to Member
JrDebugLogger - Viewer Speed
« on: March 01, 2006, 05:15:04 PM »
I have noticed that DebugMonitorViewer really hogs the CPU when messages are output in quick succession. This is quite a common occurrence in my application and it is severely affecting performance. On these occasions Task Manager shows that the DebugMonitorViewer process uses 99% of the CPU leaving nothing left for the parent application. It seems that inserting the log rows into the viewer's internal database is just too slow. Even after I exit my application I can see log rows still being added to the viewer as it catches up with the requests.

I believe that there are two issues here. One is the basic speed of adding a row. There seems to be a lot of small memory allocations as rows are added. It would help if larger blocks of memory were allocated less frequently; perhaps that could be an option if you're concerned about reserving too much memory. The second issue is the priority of the viewer process. I think it should be as low as possible by default.

Speed aside, the usefulness of the viewer constantly surprises me and I sometimes wonder how I managed without it.

Thank you.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,406
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #1 on: March 01, 2006, 07:11:53 PM »
it's so nice to hear that it's useful - i could actually fix this problem by limiting the speed of visual updates to the grid.

Reldas

  • Charter Member
  • Joined in 2006
  • ***
  • default avatar
  • Posts: 9
    • View Profile
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #2 on: March 02, 2006, 01:34:47 AM »
That would be very welcome. I'm happy to test any changes if necessary.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,406
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #3 on: March 02, 2006, 02:12:03 AM »
ill put it on to todo list and try to get it done this month.

Reldas

  • Charter Member
  • Joined in 2006
  • ***
  • default avatar
  • Posts: 9
    • View Profile
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #4 on: May 18, 2006, 03:44:05 PM »
Any news on this matter?

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,406
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #5 on: May 18, 2006, 03:46:31 PM »
sorry i forgot but ive been updating all my apps recently so expect an update *this* month :)

Reldas

  • Charter Member
  • Joined in 2006
  • ***
  • default avatar
  • Posts: 9
    • View Profile
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #6 on: May 18, 2006, 03:55:48 PM »
Thank you. I'll look forward to it. Could you address my zero-overhead post too please.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,406
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: JrDebugLogger - Viewer Speed
« Reply #7 on: May 18, 2006, 03:59:43 PM »
i *believe* that the same single solution will solve both problems. i suspect that its the constant refreshing of the display with each new row that is causing all the problems; by limiting visual update speed i am guessing the problem will be solved.