On 9/30/04 2:15 PM, "Stewart, Brian C" <[EMAIL PROTECTED]> Spew into the Cybertrough:
> Here I go... One Last Time... > > Experience has shown me that crossing the path of a List Monitor usually > ends up bad for the user, but Hey... Mom never said I was a bright kid. You are always allowed to express your opinion on any of my lists with no fear of retribution. We nannies have a very specific set of rules for kicking people. > Examples of such application services that fork instances of themselves in > memory and run as separate threaded tasks on the CPU. > - ftpd > - telnetd > - httpd > - NFS > - oracle These are all OS related Tasks. > Any command will produce a process, that process will make its way to the > CPU. You may be running two applications, my wife the graphic artist of the > house usually has 5 apps up at one time, she is constantly reformatting and > converting graphic items. > - Photo Shop is running a filter > - Quark is importing a pic and adding it to a layout > - Graphic converter is changing graphic types from one type to the other > - iTunes is running in the background > - Safari is in there somewhere, along with MSN Messenger > All the applications are running at the same time, or appear to be running > at the same time. Non of the applications have to be multi-threaded to take > advantage of the second processor. The Operating system will divide >> Two Again all you are demonstrating is a Multiprocessor "aware" OS dividing up tasks. I never said that an OS would not doll out a few OS related tasks onto a 2nd processor. The way you were painting it was completely different though. For example if you look at Bryce (or something not written for dual CPU's) you will see a few tasks immediately sent to a 2nd processor, but it is not rendering or processing a complex cut-paste. It is most likely a RAM request. Yes it will speed you up 2% or something. It will not use the 2nd processor to run a 2nd Application. > --> I must have missed the whole story of a multi-tasking multi-user > operating system. Mac OS X is BSD Unix under the covers. Perform a "ps -aux" > command from the terminal window and you will see multiple processes waiting > in the RUN QUEUE. A Dual CPU system has two CPU's as a resource so "two" > tasks can run at the exact same time. Review the output of the vmstat > command and ps commands over a duration of 1 hour and prove that your system > does not have at one point, two or more processes that are waiting in the > run queue. A great application is "TOP", It is a freeware application that > will show CPU utilization per CPU. You will see both CPUs working on a > system under moderated work load. I am well aware of TOP and Sourceforge. I have been writing code for the Mac OS for about 8 years now. > --> A process does not have to be multi-threaded to run on CPU-0 and have a > second unrelated process run on CPU-1. This is a function of the operating > system, not the application. Not true. An application has to specifically be written to allow for the splitting of commands among 2 or more processors. The OS has a few allowable tasks it takes from an App at startup, but not enough to show a speed increase. > --> A multi threaded Application is a process that can be broken down into > smaller threads that can be executed simultaneously. A multi threaded > application is a process that will run simultaneously on two or more CPUs. Exactly my point. > --> As a student of Computers of a variety of UNIX'S it is completely > irrelevant if a task is written as a multi-threaded process or not to take > advantage of a multi CPU system. Two independent processes can run > simultaneously on a dual CPU. As someone who codes I can tell you that that is 100% not the fact. Go spend a little time at the ADC site and read up. > A Dual CPU system has advantages that are leaps and bounds above a single > CPU system. Apple has dumped the single CPU G5 tower from its latest > offerings. Primarily because they have an OS that Is multi-processor aware. > I will always advocate the use of a DUAL CPU over a single CPU system. Bus > Speed, cache, double-data-rate, and other buzz words aside, Two Brains are > better then one. A single CPU system will appear laggy and unresponsive > under moderate work load. Mouse movement and keyboard commands become a > chore. Run the same work load on a slower DUAL CPU system and you will > experience a night and day difference. I have...for years. I had a 9500/180MP when it first came out. It was a dog that crashed a lot. I went back to using my 8500/120 single processor for stability. Now my Dual 2GHz G5 rocks...no argument. And I do like a dual processor architecture. I agree with Apple's move in that arena, even though the machines will be priced higher because of the 2nd processor. Kyle H. Hansen -- Jesus Saves...but Gretzky grabs the rebound and backhands for a goal!!! -- G-List is sponsored by <http://lowendmac.com/> and... Small Dog Electronics http://www.smalldog.com | Refurbished Drives | -- We have Apple Refurbished Monitors in stock! | & CDRWs on Sale! | Support Low End Mac <http://lowendmac.com/lists/support.html> G-List list info: <http://lowendmac.com/lists/g-list.shtml> --> AOL users, remove "mailto:"; Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive: <http://www.mail-archive.com/g-list%40mail.maclaunch.com/> Using a Mac? Free email & more at Applelinks! http://www.applelinks.com
