I just discovered that the QNX 6.21 login screen, with the
username/password box floating around, eats about 20-25% of a
Pentium 4 with a VESA controller. “io-graphics” is using
up way too much CPU time.
If you log in, the overhead goes way down.
Discovered this on our target system, a PC-like
embedded machine which we normally run without a
display.
Where’s the “don’t come up in Photon” setting
again? I forget. Thanks.
John Nagle
Team Overbot
touch /etc/system/nophoton (I think).
Grep for nophoton recursively under /etc, one of the scripts should mention
it, then you’ll figure it out…
“John Nagle” <nagle@overbot.com> wrote in message
news:ctekt6$3fm$1@inn.qnx.com…
I just discovered that the QNX 6.21 login screen, with the
username/password box floating around, eats about 20-25% of a
Pentium 4 with a VESA controller. “io-graphics” is using
up way too much CPU time.If you log in, the overhead goes way down.
Discovered this on our target system, a PC-like
embedded machine which we normally run without a
display.Where’s the “don’t come up in Photon” setting
again? I forget. Thanks.John Nagle
Team Overbot
“Igor Kovalenko” <kovalenko@comcast.net> wrote in message
news:ctev0e$a19$1@inn.qnx.com…
touch /etc/system/nophoton (I think).
That should be -
touch /etc/system/config/nophoton
Jim
Grep for nophoton recursively under /etc, one of the scripts should
mention it, then you’ll figure it out…“John Nagle” <> nagle@overbot.com> > wrote in message
news:ctekt6$3fm$> 1@inn.qnx.com> …
I just discovered that the QNX 6.21 login screen, with the
username/password box floating around, eats about 20-25% of a
Pentium 4 with a VESA controller. “io-graphics” is using
up way too much CPU time.If you log in, the overhead goes way down.
Discovered this on our target system, a PC-like
embedded machine which we normally run without a
display.Where’s the “don’t come up in Photon” setting
again? I forget. Thanks.John Nagle
Team Overbot
Igor Kovalenko wrote:
touch /etc/system/nophoton (I think).
Yes, found that by reading through the /etc scripts.
Really, though, the 6.21 login screen does eat way
too much CPU.
John Nagle
“John Nagle” <nagle@downside.com> wrote in message
news:ctgiq1$f9e$1@inn.qnx.com…
Igor Kovalenko wrote:
touch /etc/system/nophoton (I think).
Yes, found that by reading through the /etc scripts.
Really, though, the 6.21 login screen does eat way
too much CPU.
I haven’t check but my guess is it does it but a low priority.
John Nagle
Mario Charest wrote:
“John Nagle” <> nagle@downside.com> > wrote in message
Really, though, the 6.21 login screen does eat way
too much CPU.
I haven’t check but my guess is it does it but a low priority.
Not likely as it’s io-graphics that’s calling the driver to perform the blit that is chewing all the MIPS and io-graphics ain’t at a low priority.
Evan
“Evan Hillas” <evanh@clear.net.nz> wrote in message
news:ctig1m$rec$1@inn.qnx.com…
Mario Charest wrote:
“John Nagle” <> nagle@downside.com> > wrote in message
Really, though, the 6.21 login screen does eat way
too much CPU.
I haven’t check but my guess is it does it but a low priority.
Not likely as it’s io-graphics that’s calling the driver to perform the
blit that is chewing all the MIPS and io-graphics ain’t at a low priority.
io-graphics should adjust its priority to that of the client. That being
said, I did a quick test and phlogin doesn’t lower it’s priority when it
starts to move around…
Evan
There’s a similar Microsoft bug that’s a classic. Windows NT 4
shipped with the “Pipes” 3D screen saver on by default. There
were many headless servers using up time running that screen
saver. Worse, the servers typically didn’t have 3D hardware,
so the software implementation of OpenGL was running. This
could eat more than half the CPU.
John Nagle
Mario Charest wrote:
io-graphics should adjust its priority to that of the client. That being
said, I did a quick test and phlogin doesn’t lower it’s priority when it
starts to move around…
Is there a way to extend the timeout for the CPU hogging feature?
On my machine it more like 60% CPU usage.
I need photon running, but while I’m developing (i.e., compiling), I’d
like the CPU for myself.
BTW, I usually ssh into the machine and use XPhoton.
Thanks,
Jeff
“JeffNav” <jeff.hawk@navteq-dot-com.no-spam.invalid> wrote in message
news:d7lak9$t2d$1@inn.qnx.com…
Is there a way to extend the timeout for the CPU hogging feature?
I presume you’re referring to the “screensaver mode” of phlogin, with the
login dialog moving randomly on the screen? The -B option changes what’s
supposed to be smooth motion to big jumps once every ten seconds.
Since phlogin must be started by Photon, you’ll have to pass the phlogin
command line to Photon’s -l option. Take a look at the docs for more
details.
On my machine it more like 60% CPU usage.
With what graphics driver?
I need photon running, but while I’m developing (i.e., compiling), I’d
like the CPU for myself.BTW, I usually ssh into the machine and use XPhoton.
Thanks,
Jeff