Greate news (or bad news) that means we have not a windows issue. what happens when you switch to singelthreaded ?
/adrian 2009/2/1 Simon Loic <[email protected]> > Hi, > in my case when I am runing osgviewer on a ubuntu distribution with 4 cores > I get 25% of cpu, which means that one of my cores is over used. One of my > colleagues have exactly the same behavior. Thus I don't think this is > windows related only. > > > On Sun, Feb 1, 2009 at 2:55 PM, Glenn Waldron <[email protected]> wrote: > >> Adrian, >> >> I have observed an intermittent problem on Windows in which osgviewer >> starts up using a high CPU %, but then cycling through the threading >> modes with 'm' makes the problem go away - even when you return to the >> mode in which you started. I never did figure out why. >> >> Just a data point... >> >> >> Glenn Waldron : Pelican Mapping : http://pelicanmapping.com : >> +1.703.652.4791 >> >> >> >> On Sun, Feb 1, 2009 at 7:45 AM, Adrian Egli OpenSceneGraph (3D) >> <[email protected]> wrote: >> > Hi Cory, >> > >> > I am working with Windows Vista dual core system. I get 50% CPU usage >> when i >> > am running osgviewer cow.osg if i start >> > osgviewer cow.osg --SingleThreaded i have no longer 50% CPU usage , now >> i >> > have about 0.5-3% CPU usage !!!!! >> > >> > i am very busy at the moment, but may tomorrow i will debug the OSG >> core, >> > may there is a bug inside or a thread running at max. >> > or robert has some idea,where i can start with debugging. may it's a >> windows >> > vista bug >> > >> > adrian >> > >> > >> > 2009/2/1 Robert Osfield <[email protected]> >> >> >> >> Hi Cory, >> >> >> >> I'll have to defer to others on the situation under Windows when doing >> >> remote desktop. My guess is that it's likely to be a driver issue. >> >> >> >> Robert. >> >> >> >> On Sat, Jan 31, 2009 at 3:27 PM, Cory Riddell <[email protected]> >> wrote: >> >> > I'm not sure about vysync. I'll look that up and check it. >> >> > >> >> > I thought about the possibility of it being a debug build and I don't >> >> > think >> >> > that's it. In my bin directory I have osgviewer.exe at 25,600 bytes >> and >> >> > osgviewerd.exe at 81,920 bytes. Both executables give me the same CPU >> >> > pegging behavior (as observed by SysInternals Process Explorer). >> >> > >> >> > My command line is "osgviewer.exe --window 100 100 200 200 >> cessna.osg". >> >> > My >> >> > video card is an ATI FireGL V7700 and the drivers are up to date. >> >> > >> >> > Ah- I just noticed something-- an error message: >> >> > Windows Error #127: [Screen #0] ChooseMatchingPixelFormat() - >> >> > wglChoosePixelFormatARB extension not found, trying GDI. Reason: The >> >> > specified procedure could not be found. >> >> > >> >> > I'm running over remote desktop right now, so perhaps that's related. >> I >> >> > don't recall seeing this error message before. >> >> > >> >> > Cory >> >> > >> >> > On Sat, Jan 31, 2009 at 3:54 AM, Robert Osfield >> >> > <[email protected]> >> >> > wrote: >> >> >> >> >> >> Hi Cory, >> >> >> >> >> >> It's not normal to have this high level of CPU usage for this model, >> >> >> the expceptions to this would be: >> >> >> >> >> >> You have vysync switched off, so the app is racing as fast it can >> >> >> to dispatch frames >> >> >> You've compiled the OSG with debug build. >> >> >> >> >> >> Robert. >> >> >> >> >> >> On Fri, Jan 30, 2009 at 8:36 PM, Cory Riddell <[email protected]> >> >> >> wrote: >> >> >> > When I run the osg viewer app and load just about any osg file >> (like >> >> >> > cesna.osg), my CPU usage is a constant 23% - 30%. This is with no >> >> >> > interaction, it is basically using an entire CPU core. >> Fortunatelly I >> >> >> > have a >> >> >> > 4 core machine, so it hasn't been a problem so far, but I'm >> wondering >> >> >> > what >> >> >> > this means for single core machines (which most of our customers >> >> >> > have). >> >> >> > >> >> >> > Is this typical? >> >> >> > >> >> >> > Cory >> >> >> > >> >> >> > _______________________________________________ >> >> >> > osg-users mailing list >> >> >> > [email protected] >> >> >> > >> >> >> > >> >> >> > >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> >> > >> >> >> > >> >> >> _______________________________________________ >> >> >> osg-users mailing list >> >> >> [email protected] >> >> >> >> >> >> >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> > >> >> > >> >> > _______________________________________________ >> >> > osg-users mailing list >> >> > [email protected] >> >> > >> >> > >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> > >> >> > >> >> _______________________________________________ >> >> osg-users mailing list >> >> [email protected] >> >> >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > >> > >> > >> > -- >> > ******************************************** >> > Adrian Egli >> > >> > _______________________________________________ >> > osg-users mailing list >> > [email protected] >> > >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > >> > >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > > > > -- > Loïc Simon > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > -- ******************************************** Adrian Egli
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
