Comments on: FPS, Frame Time and you: adventures in performance.

By: Michanikos

Michanikos — Fri, 14 Nov 2008 03:16:11 +0000

Moving Average might be more usefull than a straight “since last reset” average. Should have both.

By: cubed2D

cubed2D — Fri, 28 Mar 2008 17:42:05 +0000

Thanks for the comment Eforen, what your saying there does seem to make sense. This article is ancient, and in need of an update. I dont think it will even work with xna 2.0, as they changed how the main loop executes.

Im pritty sure the code worked in the test app, it might just be a typo in the article but i have no idea it was so long ago! I think its allmost time to clear this blog out and start again

By: Eforen

Eforen — Fri, 28 Mar 2008 17:18:11 +0000

I was looking over this page and i noticed when you checked for Infinity & highestFPS you may have miss typed you put && ! (And Not) where it should be || (Or Logic Op) and check if highestFPS is infinity.

“if (currentFPS > highestFPS && !double.IsInfinity(currentFPS)) highestFPS = currentFPS;”

Else it will never be true after the first frame. For current will not ever be greater then infinity unless something goes horribly wrong and the universe starts unraveling. thus if we instead go with

“if (currentFPS > highestFPS || double.IsInfinity(highestFPS)) highestFPS = currentFPS;”

we kill 2 birds with one cpu flop as the case could be where we check for both if the currentFPS is greater then the highestFPS and if out highest is infinite we fix it by useing the currentFPS as the new highestFPS untell currentFPS is not infinite then it just checks a new highest. || if you would like to protect the highest from ever becomeing Infinity you could add your and back in and have && “if (currentFPS > highestFPS && !double.IsInfinity(currentFPS) || double.IsInfinity(highestFPS)) highestFPS = currentFPS;”

witch will stop it from ever being Infinity tho it would be good to see if somehow you got stuck in a infinite loop.

Just thought i would note that to you all.

-Eforen

By: Mike

Mike — Tue, 19 Jun 2007 16:49:17 +0000

Mike…

Cool! Its really cool….

By: 3D Game Programming » Blog Archive » Adventures in Performance II: Profiling

Wed, 06 Jun 2007 07:31:50 +0000

[...] Adventures in Performance II: Profiling Cubed2D brings news of part two in a series on Profiling in XNA games. In this article Cubed2D goes over what profilers are, how to create them as well as how to use them efficiently. Sample code is introduced in the form of a game that spits out triangles and spheres with the profiler output displayed to the window. Be sure to check out the first article on FPS and Frame Time. [...]

By: Adventures in Pefromance 2: Profiling | The NekoCake notePad

Adventures in Pefromance 2: Profiling | The NekoCake notePad — Tue, 05 Jun 2007 22:36:55 +0000

[...] FPS, Frame Time and you: adventures in performance. [...]

By: cubed2D

cubed2D — Tue, 01 May 2007 10:54:51 +0000

Thats a good idea, and will be very easy to get working, probly something like this.

time +=ElapsedGameTime.TotalMilliseconds
if (time >= 1000f)
{
This.Reset(gameTime);
}

just count up the elapsed time every frame, when it gets to your time intival (1 second in my example), call reset. reset will reset all of the stats, but you could add different overloads for it, or just add a bool/enum to it to get it to change differnt stats.

That seem good to you?

By: Jeff Weber

Jeff Weber — Tue, 01 May 2007 02:31:13 +0000

Very nice post. The only thing I might suggest is to go with your other performance values is a running average for fps and frame rate. This would display the average over the last “n” frames (n would be configurable. This might be a little more useful then the average over the entire runtime of the app.

Just a thought.