On Thu, Aug 4, 2011 at 9:09 PM, Alex Sharp <[email protected]> wrote:
> On Tue, Aug 2, 2011 at 2:54 PM, Eric Wong <[email protected]> wrote:
>> Can you try to strace (or equivalent) the old master to see what's using
>> 100% CPU?
>>
>
> All I see is a whole lot of this:
>
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
> sched_yield() = 0
Actually, my fault -- the last email was the output of new master.
Running strace on the old master shows the following:
select(4, [3], NULL, NULL, {13, 466686}) = 0 (Timeout)
wait4(-1, 0x7fff57e7bfcc, WNOHANG, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1312517345, 425411398}) = 0
fstat(9, {st_mode=S_IFREG, st_size=0, ...}) = 0
clock_gettime(CLOCK_REALTIME, {1312517345, 425625251}) = 0
fstat(11, {st_mode=S_IFREG, st_size=0, ...}) = 0
clock_gettime(CLOCK_REALTIME, {1312517345, 425779281}) = 0
fstat(12, {st_mode=S_IFREG, st_size=0, ...}) = 0
clock_gettime(CLOCK_REALTIME, {1312517345, 425927762}) = 0
The first line was when the master was idle, and then I threw a few
requests at it.
- alex
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
