• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: TCP speed versus busy processes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TCP speed versus busy processes


  • Subject: Re: TCP speed versus busy processes
  • From: Quinn <email@hidden>
  • Date: Thu, 21 Aug 2003 08:51:32 +0100

At 16:50 -0400 20/8/03, Philip D. Wasson wrote:
The sh instances have Nice level 0 and Priority 31; the setiathome instances have Nice 20, as specified in their command-line arguments, and a variable Priority (I've seen 0, 11, and 6 so far); and my app has Nice 0 and Priority 46.

OK, that's the way it should be.

(I don't know anything about Priority; the man pages I could find seemed to just talk about the Nice level, and the Darwin Kernel Programming book skirted the issue without telling me what the relationship is between Priority and Nice level.)

The priority, as reported by ps -M, is the actual priority that the kernel is running a thread, ranging from 0 (idle) to 127 (realtime). For timeshare threads (everything that you've run), the priority starts at a specific number (based on the context you run it in, GUI, non-GUI, niced) and is then lowered as the process consumes more CPU. That's why you see "sh" with priority 31 (the default for non-GUI), "seti" with a variable and very low priority (it's priority starts off low because of the "nice" and it drops as it consumes all the CPU), and your application at priority 46 (default for GUI).

So, that's all as it should be.

The thing I don't understand is why these low-priority SETI threads would affect your network response time. *shrug* Weird.

There's not much more I can contribute for a mailing list question. You might try asking on one of the darwin mailing lists, where kernel engineering folks tend to hang out. Alternatively, open a DTS incident and I can research this in detail.

S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: TCP speed versus busy processes (From: "Philip D. Wasson" <email@hidden>)

  • Prev by Date: Re: CFSocket and kCFRunLoopDefaultMode
  • Next by Date: authorizing and application for changing network setup
  • Previous by thread: Re: TCP speed versus busy processes
  • Next by thread: Internet Config from a daemon
  • Index(es):
    • Date
    • Thread