Language Selection

English French German Italian Portuguese Spanish

ATI's MultiVPU solution, don't get caught in the crossfire?

Filed under
Hardware

We'll have to give it to ATI for keeping our gaze fixed upon their new product for so long, whilst being fed all sorts of incomplete information about prospective performance and features. Now that the curtain has dropped on ATI's multi graphics processor solution we can only wonder what they have been doing for the past six months. Initially ATI commented that their solution would be a flexible and elegant one, and would, for example, work on any motherboard that has two PCIe slots, regardless of configuration. We would also be able to combine any two ATI PCIe graphics cards and get a boost in performance.

ATI was also quick to comment on NVIDIA's solution being a cumbersome one, requiring a special SLI motherboard, two identical graphics cards and last but not least an internal SLI connector to establish communication between the two cards. From looking at the ATI Crossfire solution they managed to eliminate none of these "drawbacks" as their solution has about the same requirements as NVIDIA's. You will also need a new motherboard sporting an ATI chipset with Crossfire support, a "master" graphics card that will work with any 2nd ATI PCIe graphics card and last, but not least, an external dongle to enable the two cards talk to each other.

So we are left scratching our heads, exactly how is this solution more elegant and flexible than NVIDIA's? At least NVIDIA's solution works with any 6800 or 6600 series graphics card, the Crossfire solution requires the purchase of a +$500 master card, so much for flexibility. And what's with that external dongle? An internal connector to establish communication and freeing the bracket of cable clutter and enabling a 2nd DVI or S-Video output is a far more elegant solution. By the looks of it the affordable SLI alternative that Crossfire was pitched as a few months ago has now turned into an expensive and not at all flexible solution that does not offer anything substantial over NVIDIA's. For the time being we'd suggest you stick with NVIDIA's solution and don't get caught in the crossfire.

Sander Sassen.

More in Tux Machines

Games and CrossOver

Red Hat and Fedora

Android Leftovers

Leftovers: OSS and Sharing

  • CoreOS Tectonic Now Installs Kubernetes on OpenStack
    CoreOS and OpenStack have a somewhat intertwined history, which is why it's somewhat surprising it took until today for CoreOS's Tectonic Kubernetes distribution to provide an installer that targets OpenStack cloud deployments.
  • Docker and Core OS plan to donate their container technologies to CNCF
    Containers have become a critical component of modern cloud, and Docker Inc. controls the heart of containers, the container runtime. There has been a growing demand that this critical piece of technology should be under control of a neutral, third party so that the community can invest in it freely.
  • How Blockchain Is Helping China Go Greener
    Blockchain has near-universal applicability as a distributed transaction platform for securely authenticating exchanges of data, goods, and services. IBM and the Beijing-based Energy-Blockchain Labs are even using it to help reduce carbon emissions in air-polluted China.
  • An efficient approach to continuous documentation
  • The peril in counting source lines on an OSS project
    There seems to be a phase that OSS projects go through where as they mature and gain traction. As they do it becomes increasingly important for vendors to point to their contributions to credibly say they are the ‘xyz’ company. Heptio is one such vendor operating in the OSS space, and this isn’t lost on us. :) It helps during a sales cycle to be able to say “we are the a big contributor to this project, look at the percentage of code and PRs we submitted”. While transparency is important as is recognizing the contributions that key vendors, focus on a single metric in isolation (and LoC in particular) creates a perverse incentive structure. Taken to its extreme it becomes detrimental to project health.
  • An Open Source Unicycle Motor
    And something to ponder. The company that sells this electric unicycle could choose to use a motor with open firmware or one with closed firmware. To many consumers, that difference might not be so significant. To this consumer, though, that’s a vital difference. To me, I fully own the product I bought when the firmware is open. I explain to others that they ought to choose that level of full ownership whenever they get a chance. And if they join a local makerspace, they will likely meet others with similar values. If you don’t yet have a makerspace in your community, inquire around to see if anyone is in the process of forming one. Then find ways to offer them support. That’s how we do things in the FOSS community.
  • The A/V guy’s take on PyCon Pune
    “This is crazy!”, that was my reaction at some point in PyCon Pune. This is one of my first conference where I participated in a lot of things starting from the website to audio/video and of course being the speaker. I saw a lot of aspects of how a conference works and where what can go wrong. I met some amazing people, people who impacted my life , people who I will never forget. I received so much of love and affection that I can never express in words. So before writing anything else I want to thank each and everyone of you , “Thank you!”.
  • Azure Service Fabric takes first tentative steps toward open source [Ed: Microsoft Peter is openwashing a patent trap with back doors]
  • Simulate the Internet with Flashback, a New WebDev Test Tool from LinkedIn
  • Mashape Raises $18M for API Gateway Tech
    Casado sees Mashape's Kong API gateway in particular as being a particularly well positioned technology. Kong is an open-source API gateway and microservice management technology.
  • PrismTech to Demonstrate Open Source FACE 2.1 Transport Services Segment (TSS) Reference Implementation at Air Force FACE Technical Interchange Meeting
    PrismTech’s TSS reference implementation is being made available under GNU Lesser General Public License (LGPL) v3 open source license terms.
  • How Open-Source Robotics Hardware Is Accelerating Research and Innovation

    The latest issue of the IEEE Robotics & Automation Magazine features a special report on open-source robotics hardware and its impact in the field.