Ticket #79 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Polling clients causes major fps loss while playing Source games (tf2) in Vista x64

Reported by: legoman666 Assigned to: uncle_fungus
Priority: minor Milestone: 2.4.0
Component: Monitoring system Keywords:
Cc:

Description

I am using version 2.3.1. I have a fairly decent computer; AMD x2 2.7ghz, 4gb ram, Ati HD3870. I never had this problem in xp x64 or x86, and now that I "upgraded" to Vista Ultimate x64, I have this problem. I'm thinking that this might be a problem with Vista's networking rather than a problem with fahmon, but I'm posting this here all the same.

Anyway, if I have fahmon open (can either be minimized or maximized) and am playing a game (Team Fortress 2), every time fahmon polls all of the clients in the list, my fps drops from a solid 60 to 10. It'll bounce back and forth rapidly between 60 and ~10 for maybe 15-20 seconds: until all of the clients are updated. Closing fahmon eliminates the problem.

Change History

(follow-up: ↓ 2 ) 01/05/08 17:16:03 changed by calxalot

Perhaps an option to serialize (single thread) the client updates would fix this?

(in reply to: ↑ 1 ) 01/05/08 17:28:06 changed by uncle_fungus

  • status changed from new to assigned.

Replying to calxalot:

Perhaps an option to serialize (single thread) the client updates would fix this?

I agree, that may be worth looking into. I'm interested in knowing if, when FahMon is updating, it starts using up lots of CPU time itself, or is it taken up by system processes (which would indicate a Vista networking issue)?

I know there is an outstanding issue with FahMon sometimes leaving runaway threads behind, and I wonder if these may be related.

01/05/08 18:24:41 changed by legoman666

Thanks for the suggestions, I'll give it a shot.

(follow-up: ↓ 5 ) 01/05/08 18:57:49 changed by legoman666

I just tested it; fahmon will use ~30% of a daul 2.7ghz amd x2 while reloading all of my clients (12)

(in reply to: ↑ 4 ) 01/05/08 20:03:12 changed by uncle_fungus

Replying to legoman666:

I just tested it; fahmon will use ~30% of a daul 2.7ghz amd x2 while reloading all of my clients (12)

OK, that seems ridiculously high to me. I may have to ask you to test out some svn builds in the near future if you're willing.

01/05/08 20:23:50 changed by legoman666

Sure, that'd be fine. Always willing to help in the name of ... science? just either post here so i get an email or send me an email directly to legoman666@fuse.net

01/14/08 07:56:35 changed by uncle_fungus

  • milestone set to 2.3.2.

01/28/08 15:28:58 changed by legoman666

Every time I open the program, it crashes. Here's the error message from Vista:

Problem signature:

Problem Event Name: APPCRASH Application Name: fahmon.exe Application Version: 0.0.0.0 Application Timestamp: 479895aa Fault Module Name: fahmon.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 479895aa Exception Code: c0000005 Exception Offset: 0000a461 OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 8d13 Additional Information 2: cdca9b1d21d12b77d84f02df48e34311 Additional Information 3: 8d13 Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

It seems to load a few of the clients and then goes kaput.

01/28/08 16:26:02 changed by uncle_fungus

Were you trying that with FahMon-2.3.2beta? If so, try beta2-test here: http://fahmon.net/tmp/FahMon-2.3.2beta2-test.zip (it fixes a few things like crash-on-reload when the projects database is out-of-date).

01/29/08 16:31:15 changed by legoman666

Oops. Ok, I tried the beta2. I still get the fps loss, but it only lasts for about 3-4 seconds instead of about 30. Good improvement, but I still won't keep the app open while I play tf2.

01/29/08 16:43:33 changed by uncle_fungus

Hmm, interesting. At least the CPU usage has gone down though.

Are you using the web output option and/or using "experimental" reloads?

01/29/08 16:48:28 changed by uncle_fungus

Another idea (or ideas)... have you tried setting FahMon?'s priority to low/lower, that might help the frame loss (+ these tests are an excuse to play games whilst testing software ;) ).

Another option - which won't make it into 2.3.2 - is changing the update interval (or disabling it entirely) whilst FahMon? is minimized. That would more-or-less eliminate the problem.

02/08/08 15:57:45 changed by uncle_fungus

  • priority changed from major to minor.
  • milestone changed from 2.3.2 to 2.3.3.

I'm going to demote this to minor priority and re-assign it to 2.3.3. I'm not sure if I can do anything further about CPU usage, but it's not going to block release of 2.3.2.

01/04/09 11:23:10 changed by uncle_fungus

  • status changed from assigned to closed.
  • resolution set to fixed.

This issue should now be resolved. A number of performance improvements have been made to reloading clients, and the option to reload clients in a single thread in series has been added to prevent bursty CPU usage.