A Flash Developer Resource Site

Results 1 to 4 of 4

Thread: CPU Usage

  1. #1
    Developer
    Join Date
    Apr 2007
    Location
    UK
    Posts
    324

    CPU Usage

    Just a test for those with dual processors.

    I've just been doing an experiment and just wanted to see if anyone can see the same results as me.

    http://www.fatal-exception.co.uk/test/Test.swf
    It will take a while to appear and will look weird but that's completely unimportant. Weirdly enough it seems to work much better on Firefox and Mozilla than IE(which is using Flash 10)

    When I run that SWF on my laptop, it runs at about 40% of the CPU's power, but not equally for each core. It runs on about 50% on one core and 25% on the other.
    If I run it through Flex (what I built it with) it's even weirder. It runs at 80% on one core and about 15% on the other. The core it uses to do the bulk of the work alternates too (perhaps because one is getting hot or something???).

    Is this simply normal behaviour for Windows machines? Does anyone else with a dual core machine see the unequal CPU usage?
    now known as dVyper

  2. #2
    Student
    Join Date
    Apr 2001
    Location
    -
    Posts
    4,756
    feels like 24 fps on a quadcore in Opera, like 30 fps in Firefox 3

    3% system CPU usage,- what is your actual framerate?

  3. #3
    cartoon serial killer... crazybonkers's Avatar
    Join Date
    Mar 2001
    Location
    UK London
    Posts
    114
    Tested on Pentium 4 3.20GHz and its taking up 40% cpu in IE, looks smooth enough considering the number of instances you have running imo

    OK im not dual core but anyway...
    Last edited by crazybonkers; 08-05-2008 at 01:39 AM.
    WWW.CRAZYBONKERS.COM Cartoons living close to the edge...drawn to die!

  4. #4
    Developer
    Join Date
    Apr 2007
    Location
    UK
    Posts
    324
    Hi,

    2% system usage!?!?!? I needs me a quad core!

    You can find the frameRate by pressing the grave accent key (on Windows systems this is below the ESC key). The slow speed of the test is due to the intended basic collision detection (so I could monitor the CPU in intense situations) which is going on in the background (you can see the number of checks in the panel when you press the grave accent key.
    now known as dVyper

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  




Click Here to Expand Forum to Full Width

HTML5 Development Center