Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I hear you - this one of the most annoying things - FW/USB drives all hang in the finder when opening them - even if it is on a alway-power-on mode for the external drives.

Even when they're awake? I haven't had that problem. I have them set to sleep to improve lifespan, but once they're awake, I don't have problems. The problem is that when you do certain tasks, it has to access every volume for some reason and does not do that concurrently with other Finder tasks, so it hangs!
 
It's really annoying to have a really powerful Mac Pro bottlenecked when you press "open with..." on something and have to wait for an external hard drive to wake up while Finder hangs.

Edit: I know that you can disable hard drive sleep but don't want to have them always awake, and I have already excluded them from Spotlight search.

I don't understand the issue.

Network HD -> Script -> Load Project AM -> Local HD

Work Work Work Work

Local HD -> Script -> Save Project PM -> Network HD

Rinse, Repeat
 
Even when they're awake? I haven't had that problem. I have them set to sleep to improve lifespan, but once they're awake, I don't have problems. The problem is that when you do certain tasks, it has to access every volume for some reason and does not do that concurrently with other Finder tasks, so it hangs!

I believe you are right - when they are awake its OK - btw I am using WD external drives on FW - the number of times they spin up/down is crazy.

And yes, I did select always power on - somewhere in the settings (also disk-utility I think)
 
Now if only Apple would put TWO of these in the new Mac Pro, instead of only offering a single socket configuration...

I think the point is that with OpenCL you can get your rendering/compiling/ect. performance from "graphics" card in a more 'bang for your buck/size/thermal/power package.
 
Then you probably should get a Supercomputer and get a couple of hundred, why stop at 4.

I think Apple knows what apps are going to be used on these systems the most and I think they are mostly GPU intensive or just adding more CPUs doesn't justify the added expense of requiring more space, more RAM, bigger power supply, more fans, etc. etc.

I think they decided that the ROI on what it takes puts them back into having a big expensive tower that most people won't really need the second CPU.

In order to run these MP Xeons with all of the extra stuff inside, they are now having to rely on MANY MANY fans, even water cooling and it just gets ridiculously expensive and the average user isn't going to want that.

I think they decided to get rid of certain types of bottlenecks instead and wanted to make the box smaller rather than just being another HUGE box that costs too much to mfg, and requires so much cooling, that most people aren't going to want that.

Just a hunch.

I would think that users using CAD, Animation, Graphic arts apps, NLE, etc. type apps probably won't see much difference in 2 CPUs when they would see more difference in 2 GPUs.

Pro Tools HD and HDX users don't really use the CPU, they use the cards themselves that they install and I'm sure having one 12 core processor handles a fully loaded down Pro Tools, Logic, native app where if you actually needed more CPU power, you'd be using HD and HDX cards instead.

It will be interesting to see how much the processor is actually taxed when running most applications to their fullest load levels. I wonder if the CPU will ever max out. I'm sure it will be a rare occasion.

Heck, I used an older iMac to do video conversion and would max out the CPU where I couldn't do anything. I was running multiple video conversions on a newer i5 with 16G of RAM and I'm barely taxing the CPU I have and it's just an i5. It will be interesting to see what apps doing what things will push the 12 core to the point where it's maxed out. I'm sure for those people, they should probably get a supercomputer and get something that has LOTS of processors because it's an app specifically for CPU crunching that's more supercomputing. I don't think Apple wants to play in that space since it's probably not a good ROI. That's why Apple kind of got out of those massive Supercomputer installs. Sometimes, it's best to let others spin their wheels in certain small niche markets for bragging rights.

Oh and don't forget the the bad ROI.
 
I believe you are right - when they are awake its OK - btw I am using WD external drives on FW - the number of times they spin up/down is crazy.

And yes, I did select always power on - somewhere in the settings (also disk-utility I think)

There are apps available for that. They ensure your drives don't spin down. Google and give 'em a try I'd say.
 
I don't understand the issue.

Network HD -> Script -> Load Project AM -> Local HD

Work Work Work Work

Local HD -> Script -> Save Project PM -> Network HD

Rinse, Repeat

It's a simple problem. For certain tasks, Finder requires all hard drives to be awake, including external ones. For example, say you right-click something and press "open with" (usually by accident). Finder goes and checks for applications that could open it, and that involves accessing data on an external hard drive. Finder wakes up that external hard drive from sleep. While the hard drive is waking up, which takes around 10 seconds in my case, Finder hangs because it does not do this concurrently. It's even worse when you have more than one external hard drive because it wakes them up one at a time, not at the same time.

As a result, my really fast machine is still a pain to use when I'm in that situation.

----------

Anandtech posted a list a few days ago, about $3k a pop it seems.

http://www.anandtech.com/show/7214/xeon-e52600-v2-price-list-server-ivy-bridgeep

:eek:
Dood, only 2.7GHz, slower than the AMD Athlon 4GHz for $80! (just kidding)
Still, that is insane. Some people must be pleading for a budget i5/i7 Mac Pro. I'm the perfect case, and I ended up getting a used and old model Mac Pro because I want expandability. Basically, I would be a Windows user on a custom PC if I didn't hate Windows.
 
Now can we have one of these (or better yet two) in a case that can hold expansion cards, and up-gradable aftermarket GPUs instead of coming already fitted in the trashcan,. :(
 
Really curious to see the price points on the new MP.

Also, hoping for a new display.

Bring on the 4k thuderbolt display!

I hope they also release a consumer handheld 4k camera so people can shoot some home movies for it.

lol at everyone who would say it's pointless because movies and tv shows aren't 4k yet.
 
Doesn't Moore's law say that this new Mac Pro should be at least 2x as fast as the prior one, given that is coming up on 2 years old?
 
Bring on the 4k thuderbolt display!

I hope they also release a consumer handheld 4k camera so people can shoot some home movies for it.

lol at everyone who would say it's pointless because movies and tv shows aren't 4k yet.

Why there are loads. Even the Go pro does 4K for a few hundred dollars.
 
I've had the 3930K featured in these benchmarks in my system since March 2012, over a year ago. And I'm not surprised to see it hold its own in Single Thread performance.

The nice thing about these LGA 2011 chips like the new one that will be used in the Mac Pro is I can drop that into my own system and get in on the 12 Core goodness without changing anything else.

Frankly I'm surprised Apple didn't release the Mac Pro last year using Sandy Bridge-E, there were 8 and 10 Core XEON chips they could have used available.
 
The big question for me is why doesn't iTunes take advantage of multiple cores better? Using them would make sense, or is this a design flaw in this new chip?

Interesting results. Sometimes more is just more...
 
Why are Mac fans excited about the performance of a Windows system?

Especially when they know that there will be Windows systems with two of these chips - but Apples will have only one....

Well.. They say pictures speak a thousand words.
 
The reason i can see why Apple decided not to use 2 processors is that it generates a LOT more heat, requires a bigger power supply, more cooling, and that costs MONEY. The amount of speed increase in a MP version isn't 2x

<snip>

What applications are you using or plan on using that requires more CPU than GPU that would need a second CPU? I'm just curious.

Depends on what you're doing, MD sims will see far better than a 2x rise doubling the core count, and while most MD type apps are heavily reliant on GPUs these days you still need some raw CPU power behind the vector processing to do the rest of the grunt work.

(Now you could make the argument that most people doing that work are running the main sims on big clusters and only small tests on their workstations, which is true, but doesn't change the fact that the speed increase would be *more* than 2x)
 
It's really annoying to have a really powerful Mac Pro bottlenecked when you press "open with..." on something and have to wait for an external hard drive to wake up while Finder hangs.

Edit: I know that you can disable hard drive sleep but don't want to have them always awake, and I have already excluded them from Spotlight search.

Do external hard drives take longer to wake up than internal hard drives?

Or, are you OK with having a hard drive "always awake" but only when it's internal?
 
Depends on what you're doing, MD sims will see far better than a 2x rise doubling the core count, and while most MD type apps are heavily reliant on GPUs these days you still need some raw CPU power behind the vector processing to do the rest of the grunt work.

(Now you could make the argument that most people doing that work are running the main sims on big clusters and only small tests on their workstations, which is true, but doesn't change the fact that the speed increase would be *more* than 2x)

You NEVER have even 2x the performance with doubled cores.
In fact, per core you gain in best case about 95% speed.
As more cores you have you have more management.
Beides management overhead, you only have a specific memory bandwidth. As more cores you have, as longer each core has to wait to get the data.

That means in some situations it is even worse having more cores than less cores.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.