.....oh god not another one.
Quote:I read somewhere else here that there was a decreased level of performance and a problem with games and >2 core optimisation
What the hell are you talking about?
Quote:This would only apply to OS X but has anyone looked into Apple's Grand Central Dispatch? It's a technology/library designed to make multithreading in OS X efficient as hell. I'm not sure of the technical limitations using it in relation to an emulator but in theory it would help a lot.
This doesn't help us at all. Instructions have to be emulated in a serial manner.
I don't remember what thread it was in. Is everyone here an asshole or do you feel it necessary to speak condescendingly? I don't understand why you can't just answer a question without throwing in disparaging remarks. How would using that API not increase performance? Especially when it can separate different parts of an application and give them priority, and it can also be used to have different processes that are technically independent. I think having only the active emulation process crash when something goes awry opposed to the whole application.
Never mind. You all desperately need to brush up on your people skills. It's a very long drop from that ivory tower you're standing on.
They are saying that you can't start the next instruction until the previous one has been finished because it needs the results from the previous instruction. There's very little possibility to multi-thread because you don't have all the data to work with until it has been created. With other applications, such as video transcoding, you can often start the next instruction while the last is still being done because you don't need the data from the last one to start it. It's just the way emulation works.
Quote:I don't remember what thread it was in. Is everyone here an asshole or do you feel it necessary to speak condescendingly? I don't understand why you can't just answer a question
We did answer your question. I even elaborated:
Quote:This doesn't help us at all. Instructions have to be emulated in a serial manner.
Quote:Never mind. You all desperately need to brush up on your people skills. It's a very long drop from that ivory tower you're standing on.
I'm not sure what your problem is at this point. You asked a question:
Quote:This would only apply to OS X but has anyone looked into Apple's Grand Central Dispatch? It's a technology/library designed to make multithreading in OS X efficient as hell. I'm not sure of the technical limitations using it in relation to an emulator but in theory it would help a lot.
We answered it:
Quote:... its just not as easy as you think...
and that library is nothing special
You required more elaboration:
Quote:I do understand the difficulty, I'm not entirely new to programming, I've just never written anything that has as much technical red tape as an emulator does, haha. The API is pretty beneficial for most things I've used that adopted it and I'm in the process of implementing it in a software synthesizer I've been working on and so far there have been fairly good improvements.
So we gave it to you:
Quote:This doesn't help us at all. Instructions have to be emulated in a serial manner.
You asked another question which we had already answered:
Quote:How would using that API not increase performance?
So delroth pointed out to you that we had already provided an answer to that.
Then you said:
Quote:Never mind. You all desperately need to brush up on your people skills. It's a very long drop from that ivory tower you're standing on.
As if we were all mistreating you and not answering your questions. AnyOldName3 figured that since you made that statement you probably still didn't get it so he decided to elaborate even further:
Quote:They are saying that you can't start the next instruction until the previous one has been finished because it needs the results from the previous instruction. There's very little possibility to multi-thread because you don't have all the data to work with until it has been created. With other applications, such as video transcoding, you can often start the next instruction while the last is still being done because you don't need the data from the last one to start it. It's just the way emulation works
I have yet to see this ivory tower you speak of. And I, along with everyone else here, are going to keep answering your questions with patience and diligence no matter what you make us out to be.
.....who/what are you responding to?
i think he wants to say: don't ask for the usage of more cores - buy a dual core cpu
@constantinosand: but the count of threads doesn't matter. hyperthreading doesn't decrease the clockrate