Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No worries. Why no need for Xeons?
I can certainly use more than 4 cores.
And why wouldn't I want ECC RAM, especially when PS relies a ton of it.

You don't need ECC ram for photoshop. ECC ram is really essential in situation where data integrity and validity must be assured, where a single flipped bit would invalidate the result of an operation. A single flip bit on a hires picture isn't all that important.
 
I for one have been dragging along on an old MP 3.1 in the office.
Commercial still photographer here, and fortunately we shoot mostly to a MBP... but when it comes to editing 16gb of ram and anemic graphics are painful. A new MBP is on order, and MAYBE just MAYBE 3GB/S will moot the RAM issue + eGPU. Only 4 cores though, come on.

At this point I'm torn, I've been holding off and holding off for a new MP release.
I need anew machine in the office, and patience is thin though.
As I sit and browse eBay looking at the older trashcans, I can't help but wonder about building a hackintosh.

I've done some searching, and haven't really seen anything out there with modern components and Xeon processors. It's all looking like Core chips.

Anyone else considering going down this road??

A Hackintosh for work sounds terrible. Every OS update is a possible show-stopping issue with some piece of your hardware. Better off just getting native Windows hardware at that point.
 
Let's assume that some group of engineers at Apple is focused on 7,1 nnMP development. That doesn't mean it's release is inevitable - market forecasts, margin expectations, etc will determine that.

As various new technologies and die shrunk components are released, the team could create prototypes and run simulations to present options to the bosses. Assuming this is an ongoing effort at Apple - which seems likely - then it's really a question of "when" such a beast might make sense. This is one of the reasons I come to this forum as people are often discussing the creation/availability of components that could change the equation.

As a point of perspective, is there anyone who cares to argue that 450 watts wouldn't be enough juice for a stupid fast computer 10 years from now? Yes, it's easy to cite the limitations of the nMP 6,1 - some really questionable choices were made. Yes, it's easy to cast Apple as a gadget company disinterested in the shrinking workstation space. Yes, if you need a stronger workstation ASAP, and prefer OS X, then waiting for Apple is hard to take. However, even taking all that and more into account - it's still an open question what's next. Apple has a history of rolling out new high end models based on available tech vs arbitrary sales cycles, so there is precedent.

Just sayin'
 
  • Like
Reactions: ManuelGomes
As a point of perspective, is there anyone who cares to argue that 450 watts wouldn't be enough juice for a stupid fast computer 10 years from now?
Compared to what we have today? I'm absolutely certain it would be stupid fast. I'm also absolutely certain that twice the wattage wouldn't be unusual for the high end of the workstation market in 10 years.

Just sayin'
 
Best official Mac Pro news from Apple recently - that they actually have a few Mac Pro in the design lab?
Actually using them seems to at least make the team aware of its age. Out of sight, out of update it seems in many Apple products.
 

Attachments

  • 67E8E188-6253-48F1-AD2A-4748DF544915.jpg
    67E8E188-6253-48F1-AD2A-4748DF544915.jpg
    196.4 KB · Views: 219
  • Like
Reactions: robotica
Best official Mac Pro news from Apple recently - that they actually have a few Mac Pro in the design lab?
Actually using them seems to at least make the team aware of its age. Out of sight, out of update it seems in many Apple products.
yep, there was something on 60 minutes last year showing the same part of the studio and the MacPros were being used then as well:

(screenshot-- not a video)
Screen Shot 2015-12-23 at 12.13.02 AM.png

#930
 
  • Like
Reactions: pat500000
You don't need ECC ram for photoshop. ECC ram is really essential in situation where data integrity and validity must be assured, where a single flipped bit would invalidate the result of an operation. A single flip bit on a hires picture isn't all that important.
It's also important for reliability.

You might not notice a flipped bit in an image - but if the bit is flipped in the instruction stream or in system data you could lose your work to a visit from kernel panic.
 
Compared to what we have today? I'm absolutely certain it would be stupid fast. I'm also absolutely certain that twice the wattage wouldn't be unusual for the high end of the workstation market in 10 years.

Just sayin'
Ask people from silicon industry what they think about high power GPU's/CPUs on smaller nodes. This is what you will get in response:
laughing8.jpg

Laughing-Lion.jpg

article-0-203C9DB900000578-441_964x632.jpg

http://wccftech.com/intel-xeon-e5-2699a-v4-skylake-ep-2017-launch/

I'm still hoping for Skylake-W sooner than -EP, maybe 1H'17, since Purley will be 2H.
And the nnMP will be awesome.
I'm betting Apple is putting some pressure on Intel to have the 1S procs ready early for the nnMP. I'd say we get a Mid'17 model.
There is also the possibility Apple will pick AMD for upcoming revision of their comptuers. How big chance for it? I would say 5% at best ;).

At this point I dont think logical would be thinking what Apple can do with Mac Pro. Both: Broadwell-EP and Skylake-EP are equally possible options.
 
It's also important for reliability.

You might not notice a flipped bit in an image - but if the bit is flipped in the instruction stream or in system data you could lose your work to a visit from kernel panic.

This is incredibly rare. Not saying it couldn't happen but in 35 years in IT I've yet to see a confirmed occurence.
Beside, autosave exist for a reason :)
 
A Hackintosh for work sounds terrible. Every OS update is a possible show-stopping issue with some piece of your hardware. Better off just getting native Windows hardware at that point.

I know, I agree.
And that's why I've never even considered it until now.
I've only run into one other person who used one on set, and it was a bit of a disaster.
Need to be able to turn the thing on and just go.

It's also important for reliability.

You might not notice a flipped bit in an image - but if the bit is flipped in the instruction stream or in system data you could lose your work to a visit from kernel panic.

This was also my thinking.
I get it, save save save.. but still, when on a deadline last thing needed would be lost data.
 
This was also my thinking.
I get it, save save save.. but still, when on a deadline last thing needed would be lost data.
what software are you using? is it hooked up to osx autosave/versions?

idk, all the main software i use in my work is hooked up (since leopard) and i haven't lost data since then.. as a bonus (or, THE bonus in my case), i no longer do 'save as' etc.. i no longer have folders full of incremental saves.. i mean, i don't even save anymore :) ..it's all automatic and all the versions are stored in the single working file.
 
what software are you using? is it hooked up to osx autosave/versions?

idk, all the main software i use in my work is hooked up (since leopard) and i haven't lost data since then.. as a bonus (or, THE bonus in my case), i no longer do 'save as' etc.. i no longer have folders full of incremental saves.. i mean, i don't even save anymore :) ..it's all automatic and all the versions are stored in the single working file.

And if that file get corrupted then you lose all of your incremental backups with it... Never put all your egg in one basket...
 
And if that file get corrupted then you lose all of your incremental backups with it... Never put all your egg in one basket...
it's in other places as well.

• Time machine every 24hrs. (dedicated wifi backup drive )
• dropbox (cloud drive) -- dropbox performing its own versioning as well.
• iCloud via desktop syncing (cloud drive)
• physical copies on two macs (physical drives)

all happening in the background/wirelessly but i think i'm pretty well covered ;)
 
http://wccftech.com/intel-xeon-e5-2699a-v4-skylake-ep-2017-launch/

I'm still hoping for Skylake-W sooner than -EP, maybe 1H'17, since Purley will be 2H.
And the nnMP will be awesome.
I'm betting Apple is putting some pressure on Intel to have the 1S procs ready early for the nnMP. I'd say we get a Mid'17 model.

I agree - at this point, it's worth waiting a few more months for Skylake-W. The performance increase available with the Skylake Xeons is substantial. If the current entire Xeon platform will be obsolete next year, why mess around with the current generation now?
 
Ask people from silicon industry what they think about high power GPU's/CPUs on smaller nodes. This is what you will get in response:
laughing8.jpg

Laughing-Lion.jpg

article-0-203C9DB900000578-441_964x632.jpg

There is also the possibility Apple will pick AMD for upcoming revision of their comptuers. How big chance for it? I would say 5% at best ;).

At this point I dont think logical would be thinking what Apple can do with Mac Pro. Both: Broadwell-EP and Skylake-EP are equally possible options.
Not quite sure what you're trying to say, but I'll offer this:

If you can fit x amount of performance into a neat and tidy package, there will be those who want x+y performance who don't CARE if it comes in a bigger, not so pretty package, because they NEED THE POWER. Hell, maybe they just WANT the power.

See mercedes, BMW, etc. all with stellar V8s. People still buy the V12s. This will never change, man.
 
it's in other places as well.

• Time machine every 24hrs. (dedicated wifi backup drive )
• dropbox (cloud drive) -- dropbox performing its own versioning as well.
• iCloud via desktop syncing (cloud drive)
• physical copies on two macs (physical drives)

all happening in the background/wirelessly but i think i'm pretty well covered ;)

Good for you.
 
  • Like
Reactions: flat five
Ask people from silicon industry what they think about high power GPU's/CPUs on smaller nodes. This is what you will get in response:

I'd imagine several of the technologies we use today would have provoked similar mirth 10 years ago. I'm also happy to stipulate that with Tim Cook at the helm Apple may not behave the same way it used to. Lots of posts on that subject ;-).

Just thought it was worth noting that from a wider lens, Apple's choice not to release a new MP by a certain time is not necessarily evidence of EOL.
 
Last edited:
  • Like
Reactions: H2SO4
Not quite sure what you're trying to say, but I'll offer this:

If you can fit x amount of performance into a neat and tidy package, there will be those who want x+y performance who don't CARE if it comes in a bigger, not so pretty package, because they NEED THE POWER. Hell, maybe they just WANT the power.

See mercedes, BMW, etc. all with stellar V8s. People still buy the V12s. This will never change, man.
I'd imagine several of the technologies we use today would have provoked similar mirth 10 years ago. I'm also happy to stipulate that with Tim Cook at the helm Apple may not behave the same way it used to. Lots of posts on that subject ;-).

Just thought it was worth noting that with a wider lens, Apple's choice not to release a new MP by a certain time is not necessarily evidence of EOL.
What I am saying is that very soon, the limit for SINGLE GPU might be at best 300 mm2 die size, and 150-175W TDP at max.

That is why companies, going down the line with GPUs will have to focus multi-GPU configurations on single PCB package. AMD is going to do this 100%. What will Nvidia do with this is not sure at this point of time, yet.

As has been said many times by people who design the GPUs(such as Raja Koduri from AMD), on smaller nodes there will be requirement from business AND performance perspective to use multi-GPU configurations on single PCB, rather than big, power hungry GPUs.
 
This is incredibly rare. Not saying it couldn't happen but in 35 years in IT I've yet to see a confirmed occurence.
Beside, autosave exist for a reason :)
What's the first question asked if someone complains about an unstable machine?

** Have you run a memory test ? **
 
what software are you using? is it hooked up to osx autosave/versions?

idk, all the main software i use in my work is hooked up (since leopard) and i haven't lost data since then.. as a bonus (or, THE bonus in my case), i no longer do 'save as' etc.. i no longer have folders full of incremental saves.. i mean, i don't even save anymore :) ..it's all automatic and all the versions are stored in the single working file.

sure, some of my software is capable of auto saving.
however, i don't always want it to.. photoshop is actually a perfect example of this.
the software doesn't save history states with the file, so if I make some progress in one direction, the image saves at a point, and then crash.. upon re-opening i no longer have the ability to make finite moves in a reverse direction, or sample from a state in the past.
obviously, having the work save incrementally in versions would elevate this to an extent, but it isn't realistic to constantly be writing the file to disk ever min or less. especially when you're talking multi GB files.
 
What's the first question asked if someone complains about an unstable machine?

** Have you run a memory test ? **

I've at work exponentially more instability caused by failing HDD than by failing ram. With around 30k desktop, laptop and workstation, we have only about a dozen bad dimm reported per years but hundreds of spinners going bad per years.

The situation may be different when it comes to servers but i'm not the one managing the server farm.
[doublepost=1479343007][/doublepost]
sure, some of my software is capable of auto saving.
however, i don't always want it to.. photoshop is actually a perfect example of this.
the software doesn't save history states with the file, so if I make some progress in one direction, the image saves at a point, and then crash.. upon re-opening i no longer have the ability to make finite moves in a reverse direction, or sample from a state in the past.
obviously, having the work save incrementally in versions would elevate this to an extent, but it isn't realistic to constantly be writing the file to disk ever min or less. especially when you're talking multi GB files.

Mmmm... Photoshop does have an history of modification. But not all actions can be reverted via the history as some funtions are destructive in nature.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.