Mrkebubun / o3d

Automatically exported from code.google.com/p/o3d
0 stars 0 forks source link

Beach Demo: Bad CPU Performance #132

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
OS: Leopard,Tiger
Browser: Firefox3, Firefox 3.5.2
Chipset : ATY,RadeonX1600,Nvidia GeForce 9400
O3D: 0.1.42.0

What steps will reproduce the problem?
1. Install O3D
2. Run Beach demo sample on Firefox.

Actual: Bad CPU performance. Takes around 80-98%

What is the expected output? What do you see instead?
Beach demo should run with optimal CPU performance.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ism...@google.com on 14 Sep 2009 at 5:06

GoogleCodeExporter commented 9 years ago

Original comment by kr...@google.com on 14 Sep 2009 at 5:28

GoogleCodeExporter commented 9 years ago
Ismail, is this a regression from our currently shipping plugin?

Original comment by vange...@google.com on 16 Sep 2009 at 5:08

GoogleCodeExporter commented 9 years ago
Yes. This is Regression. 

Original comment by ism...@google.com on 16 Sep 2009 at 5:24

GoogleCodeExporter commented 9 years ago
Sorry..this is consistently not repeatable. We will reopen if we identify 
proper rigid steps.

Original comment by ism...@google.com on 18 Sep 2009 at 4:38

GoogleCodeExporter commented 9 years ago
Reproducible When 
Clear cache.
Change the value for  O3D plugin Info plist element --> O3DForceSoftwareRendere 
to YES
Run the Beach demo sample.

Original comment by ism...@google.com on 1 Oct 2009 at 12:35

GoogleCodeExporter commented 9 years ago
Issue on both Safari and Firefox.

Platform:
  Hostname: Macintosh-0017f2d64524.local
  Mac OS X Version 10.5.8 (Build 9L27)
  Processor: 2 Intel 2.33 GHz
  RAM: 2048 MB

O3D:
  O3D version: 0.1.42.1  <<<Release>>>

Installed Browsers:
  Safari: 4.0.3 (5531.9)
  Firefox: 3.5.3 (3.5.3)
  Camino: 1.6.7Int (1609.03.27)

Original comment by ism...@google.com on 1 Oct 2009 at 12:40

GoogleCodeExporter commented 9 years ago
High CPU loads are expected when running with the s/w renderer.

Original comment by vange...@google.com on 1 Oct 2009 at 8:48