F
Folkert Rienstra
J. Clarke said:
Because it wanted to, obviously.
Back, BACK I say.
Rita Ä Berkowitz <[email protected]>
Rita A. Berkowitz <[email protected]>
Rita_A_ Berkowitz <[email protected]>
J. Clarke said:
Back, BACK I say.
Marc de Vries said:Well, that is just your word against mine.
I know from experience that it does not do that. Whatever you claim
otherwise in a ng doesn't change my real-world experience with the
software.
Again your word against mine.
SOME programs does this, MOST do not.
Your guess is as good as mine.
But since it is quesswork I have never claimed that that MUST be his
botteleneck. I have also never claimed that I know what would be the
best solution for his problem, because it is impossible to determine
that without knowing his bottlenecks.
Instead I have given several likely scenarios and told him to determine
which scenario fits in his case, and what that means for the hardware he
needs to buy.
What is so terrible about that?
And how would you know that?
You are also guessing. But you claim that better disk I/O will solve
every problem.
Come on Rita, be realistic.
ROTFLOL!
Knowing nothing about the current bottlenecks and then claiming that
scsi will solve all his problems, THAT is giving intentionally wrong
information.
I have given him several possible scenarios, so that he can determine
which scenario applies to him, and make the best hardware choice
without having to come back to this ng for every single step in making
that choice.
It suprises me that you don't see that.
I have found from experience that in most such cases disk I/O is not
the main culprit.
Photoshop relies on memory, memory and more memory. (and cpu)
It depends on the situation. He is not just doing videoediting, but also
photoediting. Those applications have completely different demands.
Most videoediting is done streaming, which means you don't need much
memory at all. But in the vast majority of cases that means that the
CPU is the bottleneck.
Only when you do some really simple editing which doesn't require much
cpu will the disk I/O become the bottleneck.
That might be exactly what the OP is doing, in which case he needs to
buy a SCSI array. But neither you nor I know that.
He might just have a CPU bottleneck in which case it would be wasted
money to buy SCSI.
I really don't understand why you don't want to acknowledge that.
Please explain it to me.
I know from experience that it does not do that. Whatever you claim
otherwise in a ng doesn't change my real-world experience with the
software.
Your guess is as good as mine.
But since it is quesswork I have never claimed that that MUST be his
botteleneck. I have also never claimed that I know what would be the
best solution for his problem, because it is impossible to determine
that without knowing his bottlenecks.
Instead I have given several likely scenarios and told him to
determine which scenario fits in his case, and what that means for the
hardware he needs to buy.
What is so terrible about that?
And how would you know that?
You are also guessing. But you claim that better disk I/O will solve
every problem.
Come on Rita, be realistic.
Knowing nothing about the current bottlenecks and then claiming that
scsi will solve all his problems, THAT is giving intentionally wrong
information.
I have given him several possible scenarios, so that he can determine
which scenario applies to him, and make the best hardware choice
without having to come back to this ng for every single step in making
that choice.
It suprises me that you don't see that.
That might be exactly what the OP is doing, in which case he needs to
buy a SCSI array. But neither you nor I know that.
He might just have a CPU bottleneck in which case it would be wasted
money to buy SCSI.
I really don't understand why you don't want to acknowledge that.
Please explain it to me.
Folkert Rienstra said:
Because it wanted to, obviously.
The whole point is that it should never be guesswork. But, we both know
that the disk I/O is the bottleneck.
Which is great, while generic in nature, it does give him some points to
ponder.
While not terrible, it's not productive either.
I never claimed, "better disk I/O will solve every problem". But, I did say
that he would definitely have better overall performance, which we both know
is indisputable.
I am.
And claiming that he has bottlenecks that most likely don't exist and
discounting SCSI as an option to boost his performance is intentionally
giving out wrong information
Which may or may not apply to him at all.
The same can be said about the Mem/CPU.
I guess both of us will really
never know.