Welcome to the MacNN Forums.

eddiecatflap · Jan 30, 2003, 02:33 AM

..it seems slow nad buggy in x - espec. with java enabed .. any ideas as to speed tips ?

CharlesS · Jan 30, 2003, 02:39 AM

Here's a great speed tip - don't use IE.

Use either Chimera or Safari if you want speed.

someone_else · Jan 30, 2003, 12:58 PM

Originally posted by eddiecatflap:
..it seems slow nad buggy in x - espec. with java enabed .. any ideas as to speed tips ?

IE is a dog. It is multi-threaded, but the thread's it uses are the Mac OS 9 flavor known as cooperative threads. This means that a thread must specifically yeild processor time so other threads can run. Pretty useless if you ask me.

As Charles said, use Chimera.

Vanquish · Jan 30, 2003, 03:15 PM

*spits on IE*

clarkgoble · Jan 30, 2003, 03:30 PM

IE uses cooperative threads? I didn't know Carbon did that. One would have thought that Apple would have mapped co-operative threads onto real threads. After all even with the old co-operative threads you still have to worry about mutex and such things.

Developer · Jan 30, 2003, 03:47 PM

Originally posted by clarkgoble:
IE uses cooperative threads? I didn't know Carbon did that.

Carbon apps can use cooperative threads, MPThreads, or pthreads (the last on X only).

Originally posted by clarkgoble:
One would have thought that Apple would have mapped co-operative threads onto real threads. After all even with the old co-operative threads you still have to worry about mutex and such things.

That's exactly what they did.

voodoo · Jan 30, 2003, 05:03 PM

There are still times I have to use IE, not that I enjoy it particularily. I think I've just gotten used to having 3 or 4 browsers on my iBook. I use Mozilla on these forums, Safari for almost anything else and Navigator for the occational browse. And sometimes IE. But IE is slow, and there is nothing anyone can do about it. Perhaps there will be a significant speed difference when/if MS releases IE 6 for Mac.

soellman · Jan 30, 2003, 06:09 PM

Originally posted by Vanquish:
*spits on IE*

you are one classy broad..

someone_else · Jan 30, 2003, 06:39 PM

Originally posted by clarkgoble:
One would have thought that Apple would have mapped co-operative threads onto real threads. After all even with the old co-operative threads you still have to worry about mutex and such things.

As Developer pointed out, Apple did do that. But all coop threads (within a process) share one global lock. Each coop thread blocks on this lock when it wants to run. When a thread aquires the lock, it can run forever, or for a short period of time. The global lock is how they provide the coop thread behavior on top of pre-emptive threads.

[APi]TheMan · Jan 30, 2003, 07:07 PM

Originally posted by eddiecatflap:
..it seems slow nad buggy in x - espec. with java enabed .. any ideas as to speed tips ?

Wow, I'm surprised you aren't in the know with the browser stuff. The majority of users here on these boards will use Safari, Chimera, or some other Netscape derivative.

Most people don't use IE... Myself, I use Internet Explorer with my school's portal about once a semester to check my grades...

Phoenix1701 · Jan 31, 2003, 02:40 AM

Originally posted by someone_else:
As Developer pointed out, Apple did do that. But all coop threads (within a process) share one global lock. Each coop thread blocks on this lock when it wants to run. When a thread aquires the lock, it can run forever, or for a short period of time. The global lock is how they provide the coop thread behavior on top of pre-emptive threads.

Perhaps I'm misunderstanding, but if all but one of the threads in the process block while the other thread runs until the process's time slice expires, doesn't that completely and totally defeat the purpose of using threads in the first place, especially on multiprocessor machines...? The programmer should have taken care of synchronization issues when they multithreaded the program to begin with, so why not let more than one thread be in the ready queue at once?