psxss.exe using 50-90 % CPU

	Free Downloads, Community Forum, FAQs and Developer Resources

Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums	Register	Login	Search	Subscriptions	My Profile	Inbox
Tool Warehouse	FAQs	Resources	Help	Member List	Address Book	Logout

psxss.exe using 50-90 % CPU

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [SFU / Interix / SUA Technology] >> Interix Advanced Forum >> psxss.exe using 50-90 % CPU

Page: [1]

Message

<< Older Topic Newer Topic >>

psxss.exe using 50-90 % CPU - Jul. 20, '06, 5:00:15 PM

gregmb

Posts: 27
Status: offline

I'm running SFU 3.5 on XP SP2, with HotFix 914680 installed from MS.

I see something strange which maybe some can shed light on.

I have a process that forks 4 other processes.
Both the parent and children are threaded (Posix threads),
all use sockets in one form or another.

When these processes are idle, (pended in a sigwait(), or accept(), or
pthread conditional variable) they are using ~ 20% of the CPU and
the psxss.exe is using 50-90% of the CPU.

When these applications are on Linux (RedHat 4.0) or Solaris (9)
they use no CPU at idle.

What is going on here in SFU?

Greg

Post #: 1

RE: psxss.exe using 50-90 % CPU - Jul. 20, '06, 5:12:57 PM

Rodney

Posts: 3714
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

Just for confirmation: you know the processes in these states by using pstat? Or some other way?
I don't know if it's possible for your programs, but is it possible to narrow it down to a single process
that's causing the large CPU usage? <-- I thinking this might help in getting a fix from MS if needed.

(in reply to gregmb)

Post #: 2

RE: psxss.exe using 50-90 % CPU - Jul. 20, '06, 6:26:36 PM

gregmb

Posts: 27
Status: offline

Interesting I did a truss on one of the processes, and one of it's
threads is continually calling pthread_mutex_lock() and pthread_mutex_unlock().

pstat shows the threads pended in select(), sigwait(), recvfrom(), accept()

there is one thread that seems to be running, but it doesn't look like one
I created.

I'll have to take a closer look at it.

Greg

(in reply to Rodney)