lkml.org 
[lkml]   [2008]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: x86: 4kstacks default
Date
On Sunday 20 April 2008 16:01:46 Andi Kleen wrote:
> > These are real customer workloads; java based "many things going on" at a
> > time showed several thousands of threads fin the system (a dozen or two
> > per request, multiplied by the number of outstanding connections) for
> > *real customers*.
>
> Several thousands or 50k? Several thousands sounds large, but not entirely
> unreasonable, but it is far from 50k.
>

At 12 threads per request it'd only take about 4200 outstanding requests. That
is high, but I can see it happening. At 24 threads per request the number of
outstanding requests it takes to reach that is cut in half, to about 2100.
That number is more realistic. Since all outstanding requests aren't going to
be at the extremes, let us assume that it's a mid-point between the two for
the number of outstanding requests - say somewhere around 3150 outstanding
requests.

While that is a rather high number, if a company - a decently sized one - is
using a piece of Java code internally for some reason they could easily have
that level of requests coming in from the users. For a website with a decent
load that routes a common request to the machine running the code it'd be
even easier to hit that limit. So yes, 50K threads *IS* actually pretty easy
to reach and could be a common workload.

> > That you don't take that serious, fair, you can take serious whatever you
> > want.
>
> No I don't take 50k threads on 32bit serious. And I hope you do not
> either.

Just makes you sound foolish. Run the numbers yourself and you'll see that it
is easy for a machine running highly threaded code to easily hit 50K threads.

<snip>
> > Yes 2.4 sucked a lot more than 2.6 does. But even 2.6 will (and does)
> > have fragmentation issues. We don't have effective physical address based
> > reclaim yet for higher order allocs.
>
> I don't see any evidence that there are serious order 1 fragmentation
> issues on 2.6. If you have any please post it.

Due to me screwing up the configuration of Apache (2) and MySQL I have seen a
machine I own hit problems with memory fragmentation - and it's running a 2.6
series kernel (a distro 2.6.17)

Because I was able to see that it was a problem I caused I didn't even *THINK*
about posting information about it to LKML. I didn't keep the logs of that
around - it happened more than three months ago and I clean the logs out
every three months or so.

DRH

--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.


\
 
 \ /
  Last update: 2008-04-20 22:45    [W:0.122 / U:23.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site