"New Macs for 2010 are going to take Apple to the next level"

[beaker7]

I'm not familiar with that benchmarking program.

My comment is based one compiled results from the forum under Cinebench, which was conveniently made into a chart by another member.

For most users it holds true. In probably 90% of situations the 2008 3.2 will be faster.

Benchwell is based on Maxwell Render, a ludicrously well-threaded rendering application that scales nearly linearly with cores and ghz.

 

[nanofrog]

For most users it holds true. In probably 90% of situations the 2008 3.2 will be faster.

Benchwell is based on Maxwell Render, a ludicrously well-threaded rendering application that scales nearly linearly with cores and ghz.

I looked at the page for it (About section), but I don't know any more details than that (i.e. how well does it scale with the differences in memory architecture - DDR2 dual channel vs. DDR3 triple channel).

As you say, with most, Cinebench's results would apply, particularly since there's precious little software that can actually utilize DDR3 in a triple channel configuration. But what does, can benefit substantially with the Nehalem architecture vs. Penryn used in the older MP's.

 

[TheStrudel]

But ultimately, it was mentioned to illustrate Apple's desire to have proprietary systems.

I just wanted to bring up that it wasn't, and remains definitely not proprietary (anybody can use it as part of the spec). I think that was true for mini-DVI as well since other companies could make the adapters.

Unique to ? Sure. But please don't say proprietary. It drove me nuts how they said AAC was "Apple's proprietary" in tech websites and elsewhere for years, when it never was. It's only proprietary if they lock the tech down under their control and is not part of an open standard;  certainly never owned AAC.

This may sound like nitpicking, and it may well be, but it's annoying to see that spread around.

 

[nanofrog]

I just wanted to bring up that it wasn't, and remains definitely not proprietary (anybody can use it as part of the spec). I think that was true for mini-DVI as well since other companies could make the adapters.

Unique to ? Sure. But please don't say proprietary. It drove me nuts how they said AAC was "Apple's proprietary" in tech websites and elsewhere for years, when it never was. It's only proprietary if they lock the tech down under their control and is not part of an open standard;  certainly never owned AAC.

This may sound like nitpicking, and it may well be, but it's annoying to see that spread around.

I'm looking at it from it's origins. They took a royalty free standard, and made a custom connector (eliminating the audio). The signal specs such as voltages, frequencies, bandwidth,... didn't really change.

They later opened it to the public. But it's not caught on yet, and is essentially exclusive to Apple (though there is a 5870 with 6x MDP's on it to solve the space problem that existed with that many of the larger DisplayPort connectors on a dual PCI bracket and still allow for venting).

But in terms of monitors, I've not spotted a single non-Apple unit that has a MDP connector in it. DisplayPort, yes, and can be used with an adapter (others as well, but the MDP to DVI requires circuits so isn't nearly as inexpensive as MDP to DP).

 

[TheStrudel]

I'm pretty sure the Samsung 6-monitor eyefinity setup with reduced bezels is probably going to use MDP too. But we'll see more stuff pop up as time goes by. Also, can't MDP carry sound, but  just doesn't have software support for it? So only OS X can't get it?

 

[nanofrog]

I'm pretty sure the Samsung 6-monitor eyefinity setup with reduced bezels is probably going to use MDP too.

Dunno, as I've not looked into it.

But we'll see more stuff pop up as time goes by. Also, can't MDP carry sound, but  just doesn't have software support for it? So only OS X can't get it?

The pin count and signals are technically the same, but Apple changed the pin-outs, and the signals won't match up. (MDP wiki and DP wiki both have the pin-outs listed).

There's a good chance they never created the software on their end, and they don't care about other developers (hardware or software). There are work-arounds with other interface buses (USB, TOSLINK, or FW), but none allow the audio signals to be carried on the MDP cables.