Skip to content

1,784,593 the highest load average ever?

July 22, 2009

As I cycled home I realised there was one more thing I could do on the exploring the limits of threads and processes on Solaris. That would be the highest load average ever. Modifying the thread creator program to not have each thread sleep once started but instead wait until all the threads were set up and then go into an infinite compute loop that should get me the highest load average possible on a system or so you would think.

With 784001 threads the load stabilised at:

10:16am  up 18:07,  2 users,  load average: 22114.50, 22022.68, 21245.781

Which was somewhat disappointing. However an earlier run with just 780,000 threads managed to peak the load at 1,784,593 while it was exiting:

 7:44am  up 15:35,  2 users,  load average: 1724593.79, 477392.80, 188985.10

I’ still pondering how 780000 thread can result in a load average of more than 1 million.

Advertisements

From → Solaris

4 Comments
  1. 6620948 had some pretty high load averages too – shame I didn’t get a chance to see what it peaked at.
    # uptime
    6:35pm up 1 day(s), 11:10, 1 user, load average: 4572.46, 8388608.00, 8388608.00

  2. Given that you can’t get more then 800000 threads on a system I can’t see how we could ever have a load average more than 800000. Makes me wonder about that bug, whether the load average was in anyway truthful.

  3. I would guess, that the load factor counting could get confused by thread waiting two times in one timeslice.
    In OS-9/68k you could easily test this with a sleep(0), which did not sleep at all, but took the process to the end of the current processor queue.
    Since the machines does more task switches a second than 780000 you would end up with ridiculous load factors.
    It’s just a guess, since load factor processing is not bound to time slices with microstate accounting switched on.

  4. I remember fixing
    4756989 uptime output negative on a stressed system.
    Which was a negative load average on a stressed 25k. In reality before this fix it would read negative after 32768.
    alan.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: