Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 35

Thread: Low fps even on empty canvas.

  1. #21
    Junior Member
    Join Date
    Dec 2009
    Posts
    9

    Re: Low fps even on empty canvas.

    aho
    Thank you for detailed response!

  2. #22
    Junior Member
    Join Date
    Jun 2010
    Posts
    7

    Re: Low fps even on empty canvas.

    Just wanted to add another observation: I've found that using setInterval in my rendering code seems to slow it down artificially. For example: If I use a setInterval with a delay of 10 I should theoretically be limited to 100FPS, but on my projects I'll typically only get 45 - 50. If I change up the event that triggers a draw, though (like using Vladimir's postMessage hack) I can get much higher framerates.

    Using that method for my Quake 3 demo, which is rendered at 854x480, I can typically get ~120FPS in Chrome 6, which isn't too shabby for a fully rendered scene like that!

    I don't know that this method is appropriate for all WebGL uses, but it seems to at least get you get a better idea of your maximum potential frame rate.

  3. #23
    Junior Member
    Join Date
    Jan 2010
    Posts
    2

    Re: Low fps even on empty canvas.

    It's a shame WebGL is dragging it's heals a bit on this issue.

    "Tight integration with HTML content, including layered compositing, interaction with other HTML elements[...]"

    This isn't what 3D content needs at all. What we need is a full screen hardware accelerated canvas, otherwise the battle is lost before it begins.

  4. #24
    Junior Member
    Join Date
    Jan 2011
    Posts
    1

    Re: Low fps even on empty canvas.

    Quote Originally Posted by aho
    The forum software just decided to throw my edit away. Great.

    "Very slow" = ~27fps with older Chromium builds, ~85fps with a very recent one. While taking 100% CPU for drawing an empty 800x600 window.

    Without compositing the CPU usage would be below 1% at this framerate.

    If we want full screen gaming and good performance (=lower energy consumption) on mobile devices, we really need a way to bypass the compositing completely.
    I agree. hopefully they will address this and add a flag for bypassing the compositing.

  5. #25
    Senior Member
    Join Date
    May 2010
    Posts
    207

    Re: Low fps even on empty canvas.

    Quote Originally Posted by Cork
    It's a shame WebGL is dragging it's heals a bit on this issue.

    "Tight integration with HTML content, including layered compositing, interaction with other HTML elements[...]"

    This isn't what 3D content needs at all. What we need is a full screen hardware accelerated canvas, otherwise the battle is lost before it begins.
    I disagree. Having actually produced a full 3D game using this technology rather than just talking about it in the abstract (see http://tubagames.net), I know that using HTML5 for menus and such like is extremely useful.

    The issue is certainly with compositing - and the difficulty is that right now, not all browsers are using OpenGL or Direct3D for compositing - and that's an obvious issue at higher screen resolutions. However, it's getting fixed - albeit sporadically. Some browsers on some hardware and under some OS's have it (and I get 30Hz frame rates for a pretty complex scene) - and others don't (and I get a miserable 8 to 10Hz - even on pretty good hardware).

    It's getting better.

    While full-screen has its' uses - I doubt that more than a small percentage of 3D content (note that content!=games in many cases) will want to use it.

    The market these days is in casual games - and casual gamers don't want full-screen - they want to be able to tweet their buddies, surf the net, play the game...and occasionally do the work that their bosses are paying them to do...all at the same time.

  6. #26

    Re: Low fps even on empty canvas.

    Ive gotta agree with Steve here.
    Whilst I agree framerate is pretty poor ATM (it will improve though(*)), being able to integrate html stuff with webgl stuff is a point of difference with standard 3dapi implementations eg opengl native apps, otherwise youre better of writing a native app

    Personally though I could live without the html5 integration. But I wouldnt like to see it removed

    (*)If youre using chrome make sure youre doing
    --enable-accelerated-compositing

  7. #27

    Re: Low fps even on empty canvas.

    Also I believe once webgl is mainstream (next month perhaps) things will get faster very quick

    ATM(*) the last time I checked chrome renders webgl over twice the speed of firefox, now when websites start benchmarking webgl applications and browser X is performing terrible, the makers are gonna be so embarrassed with the benchmark results they'll do something about it.
    Look at javascript performance over the last ~year.
    chrome comes out + is 10x faster than the others, forcing all the other browsers to up their gameplay, I predict exactly the same senerio with webGL, web sites love benchmarks.
    This will be a new arms race

    (*) well chromium doesnt run webgl at all for me ATM so has a FPS of zero

  8. #28
    Senior Member
    Join Date
    May 2010
    Posts
    207

    Re: Low fps even on empty canvas.

    The problem with benchmarking right now is that the performance depends rather drastically on the application.

    * If your application is CPU-bound then JavaScript performance will be the determining factor.
    * If you render at high resolution then the efficiency of the compositor system becomes paramount.
    * If you make a ton of GL calls - then the efficiency of the WebGL implementation itself becomes critical.
    * If your platform choice requires that the system use Direct3D to emulate OpenGLES - then you're going through ANGLE - and the performance of that layer becomes critical - and comparing it to a browser that can use OpenGL when available is exceedingly problematic.
    * If one implementation offers some extension that the other doesn't - then even if it's worse at all of the previous things - it may turn out to be faster running your application simply because the extension offers a more efficient way to do something in your niche situation.
    * ...and no matter what, different GPU and CPU hardware choices will alter the balance between those things - so even if you pick a "fair" benchmark to run, the results may vary widely between users.

    Characterizing the performance of graphics systems is an exceedingly tricky matter.

    The problem will be that (in all likelyhood) each browser will lay claim to being fastest in one or other of those areas and thereby demand the title "Fastest WebGL"...and with some justification for that subset of applications that uses it!

  9. #29
    Junior Member
    Join Date
    Jan 2011
    Posts
    8

    Re: Low fps even on empty canvas.

    This is an interesting blogpost on this topic. It is mentioned, why the framerate in firefox is limited.
    http://hacks.mozilla.org/2010/08/more-e ... tionframe/

    Also, here is a site which seems to test the max number of available frames (just a guess). I dont know why this was just open in my browser right now and how I got there, but I might be of interest. BTW it slows down the browser A LOT.

    http://people.mozilla.com/~vladimir/misc/ctest3d.html

    Also again, this is probably the way to send optional attributes to the context request:

    var ctx = WebGLUtils.setupWebGL(canvas,
    {alpha : true ,
    antialias : false ,
    depth : true ,
    stencil : false ,
    premultipliedAlpha: false }));

    I'm not really at the point where I have tested them but I read somewhere that the antialias is working in some os/browser combination, so maybe the others do too.

    Have a nice day.

  10. #30
    Senior Member
    Join Date
    May 2010
    Posts
    207

    Re: Low fps even on empty canvas.

    I've only seen the antialias setting work in Chrome under Windows - it doesn't work under Firefox because of the way the image is composited. Chrome doesn't do it under Linux - presumably because they didn't implement an OpenGL path for it yet...which probably means it won't work on MacOS either.

Page 3 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. Low FPS
    By ninjanesto in forum OpenGL ES general technical discussions
    Replies: 1
    Last Post: 04-21-2006, 01:52 AM

Posting Permissions

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