or Connect
AppleInsider › Forums › Mac Hardware › Future Apple Hardware › Final curtain call for PowerPC-based PowerBooks?
New Posts  All Forums:Forum Nav:

Final curtain call for PowerPC-based PowerBooks? - Page 6

post #201 of 211
Quote:
Originally posted by The One to Rescue
Quoted from the book "High Performance MySQL", chapter 6, "Server Performance Tuning" : "This all means that the first bottleneck you're likely to encounter is disk I/O."

However, thread handling also seems to be an issue, and it seems to be a FreeBSD flaw : "Another popular free operating system, FreeBSD, has threading problems that are much worse. Versions prior to 5.2 provide rather weak native threading. In some circumstances, I/O-intensive threads are able to get an unfair amount of CPU time, thus keeping other threads from executing as quickly as they should. Given the I/O-intensive nature of some database queries, this has a rather devastating affect on MySQL."
(EDIT : by the way, I don't know what the thread handling scheme is, in Mac OS X. Does it use an approach similar to FreeBSD? Anyway, seems like OS X suffers the same threading performance problems than FreeBSD)

Hope this will help...

This issue is the thread handling. Disk I/O hasn't been a problem except for Firewire 800 on the Powermac. I forget which, either the reads or writes are slow.
post #202 of 211
Quote:
Originally posted by melgross
This issue is the thread handling. Disk I/O hasn't been a problem except for Firewire 800 on the Powermac. I forget which, either the reads or writes are slow.

Care to provide links to prove that?
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
post #203 of 211
Quote:
Originally posted by The One to Rescue
Care to provide links to prove that?

Not at this time at night it's 2.33 a.m. here. I'll try to check tomorrow morning.

And the polite word is "show". I don't have to "prove" anything to you. As you think you know, you can always look it up yourself. You already provided my "proof" yourself.
post #204 of 211
Quote:
Originally posted by melgross
Not at this time at night it's 2.33 a.m. here. I'll try to check tomorrow morning.

And the polite word is "show". I don't have to "prove" anything to you. As you think you know, you can always look it up yourself. You already provided my "proof" yourself.

Sorry, to me, "care to provide a link?" was more polite than "care to show me a link?" or "show me a link". I'm French by the way, sorry if I can't speak as perfectly as you folks.
Didn't mean to be rude anyway...
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
post #205 of 211
english is a very rude and confusing language anyway for example using the word 'root' a lot when in australia is not a good idea...

seriously though, Rescue, i think melgross is suggesting to say instead of
"Care to provide links to prove that?"

to say
"Care to provide links to show that?"

you may also say
"Care to share some links to show that?" but actually this may be considered sarcastic to some english speakers, suggesting that a person has links that he doesn't feel he wants to share with others.

So,
we'll take it as you mean
"Care to provide links to show that thread locking is more of the issue rather than i/o handling with regards to mysql performance on osXserver ?"
post #206 of 211
"However, thread handling also seems to be an issue, and it seems to be a FreeBSD flaw : "Another popular free operating system, FreeBSD, has threading problems that are much worse. Versions prior to 5.2 provide rather weak native threading"

AFAIK mac os X has a "shared heritage" with FreeBSD, the details of which probably are a whole 'nother thread. this would suggest that mac os x may have "inherited" threading problems.... so i guess what we all would be looking for is some document, if anyone has it around, that shows that threading is more of the bottleneck than i/o handling...

anyway at this stage since i am in over my head with this OS-level unix variant geekspeak, i politely make my exit... *runs to the nearest door*

*peeks through the window*
WHERE are the bloody new powerbooks ???!!
post #207 of 211
Quote:
Originally posted by sunilraman
english is a very rude and confusing language anyway for example using the word 'root' a lot when in australia is not a good idea...

seriously though, Rescue, i think melgross is suggesting to say instead of
"Care to provide links to prove that?"

to say
"Care to provide links to show that?"

you may also say
"Care to share some links to show that?" but actually this may be considered sarcastic to some english speakers, suggesting that a person has links that he doesn't feel he wants to share with others.

So,
we'll take it as you mean
"Care to provide links to show that thread locking is more of the issue rather than i/o handling with regards to mysql performance on osXserver ?"

Hey thanks a lot for the private English lesson I'll be careful next time!
Actually, the question is : Someone care to provide links to show how thread management is done in Mac OS X and how it can ruin the speed of some apps like MySQL Server?

Is it ok this time?
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
post #208 of 211
yeah that sounds alright ... in any case you should be careful about learning english from me, because i speak a mixture of californian/ australian/ british/ malaysian/ singaporean english.

hey i found this link about this guy talking about freeBSD threading
http://jeremy.zawodny.com/blog/archives/000203.html
post #209 of 211
Quote:
Originally posted by The One to Rescue
Hey thanks a lot for the private English lesson I'll be careful next time!
Actually, the question is : Someone care to provide links to show how thread management is done in Mac OS X and how it can ruin the speed of some apps like MySQL Server?

Is it ok this time?

Perfect. By the way, I just got home. I'll see if I can find something different at some point today, but really, the links to the BSD sites does tell the tale.
post #210 of 211
Quote:
Originally posted by sunilraman
yeah that sounds alright ... in any case you should be careful about learning english from me, because i speak a mixture of californian/ australian/ british/ malaysian/ singaporean english.

hey i found this link about this guy talking about freeBSD threading
http://jeremy.zawodny.com/blog/archives/000203.html

I just read this link. It's pretty good. Of course OS X uses the Mach kernel. It can access two (and with 10.4, more) cpu's for this purpose. Otherwise it's a good description.
post #211 of 211
Quote:
Originally posted by melgross
I just read this link. It's pretty good. Of course OS X uses the Mach kernel. It can access two (and with 10.4, more) cpu's for this purpose. Otherwise it's a good description.

But is Darwin's implementation of threading exactly the same as FreeBSD's implementation? It seems like the answer is yes, but I'm quite shocked that threads from the same process can't be dispatched to several CPUs on SMP configs.

According to this technote from Apple (http://developer.apple.com/technotes/tn/tn2028.html), there is support for both Linux-like and FreeBSD-like thread scheduling in OS X, the Free-BSD like (cooperative) approach being here to ensure that Carbon apps will run well.
However, the document claims that the information it gives are "highly simplified"...

All links are very welcome guys (and I sure would mind Kickaha or Programmer taking part of this conversation).
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
Basically everything goes round. We're 80% dinosaur.
-- Alex James
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Future Apple Hardware
AppleInsider › Forums › Mac Hardware › Future Apple Hardware › Final curtain call for PowerPC-based PowerBooks?