mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "Mikael Starvik" <mikael.starvik@axis.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Very long startup time for a new thread
Date: Mon, 17 Jul 2006 10:44:58 +0200	[thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C668038E9BBF@exmail1.se.axis.com> (raw)

Thanks to all that have made suggestions. Finnaly we found that 

#define MIN_TIMESLICE 5
#define DEF_TIMESLICE 25

works much better for us. Maybe it is an effect of that we have HZ=100 ?

/Mikael

-----Original Message-----
From: Mikael Starvik [mailto:mikael.starvik@axis.com] 
Sent: Thursday, July 13, 2006 8:08 AM
To: 'Linux Kernel Mailing List'
Subject: Very long startup time for a new thread


(This is on a 200 MIPS embedded architecture).

On a heavily loaded system (loadavg ~4) I create a new pthread. In this
situation it takes ~4 seconds (!) before the thread is first scheduled
in (yes, I have debug outputs in the scheduler to check that). In a 2.4
based system I don't see the same thing. I don't have any RT or FIFO
tasks. Any ideas why it takes so long time and what I can do about it?

Appreciate any help
/Mikael

             reply	other threads:[~2006-07-17  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  8:44 Mikael Starvik [this message]
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66803F33440@exmail1.se.axis.com>
2006-07-13  7:51 ` Mikael Starvik
  -- strict thread matches above, loose matches on Subject: below --
2006-07-13  6:07 Mikael Starvik
2006-07-13  7:14 ` Arjan van de Ven
2006-07-13  7:36 ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BFECAF9E178F144FAEF2BF4CE739C668038E9BBF@exmail1.se.axis.com \
    --to=mikael.starvik@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®