System Builder Marathon, December 2010: Value, Compared

By Thomas Soderstrom
published

New benchmarks, new test methods, and new hardware mark exciting updates to this month’s System Builder Marathon. Today, we cover the most exciting part of all: the value competition. Remember, we're giving all three systems away, so enter to win them!

Benchmark Results: S.T.A.L.K.E.R.: Call Of Pripyat

The S.T.A.L.K.E.R.: Call of Pripyat (standalone) benchmark scales similar to Just Cause 2, but with higher resolutions, hitting each system a little harder.

The $500 machine appears playable through our higher Call of Pripyat benchmark settings, but looks are usually deceiving in this bench. Minimum frame rates are usually around 1/3 of the average scores, so a builder would be lucky to see the $500 overclocked configuration play smoothly through 1680x1050 on the toughest maps.

Thomas Soderstrom
Thomas Soderstrom
Thomas Soderstrom is a Senior Staff Editor at Tom's Hardware US. He tests and reviews cases, cooling, memory and motherboards.
78 Comments Comment from the forums
  • Tamz_msc
    This month's 500$ build is of great value for someone on a budget.
    Reply
  • shovenose
    im going to make my mom enter so i can win one :)
    Reply
  • dEAne
    I will count on that, this is something I can compare with my other build. thanks tom.
    Reply
  • wribbs
    I really enjoy these SBM articles but you need to start putting out these systems/articles faster because by the time you post these configs no one would build them. These "December" systems all use November parts. When you know an important part (CPU/GPU) is going to be replaced by a newer model before the article will post, just wait a few days for it.
    That said, SSD is a great addition as well as some of the other difficult to measure in value parts.
    Reply
  • Your 'flexible' statistics are a joke! We'd really like the $2000 system to win to so we'll shovel in the hard drive figures with massive over-emphasis... It's bollocks.
    Reply
  • Twoboxer
    I don't understand introducing SSDs into these builds. Buying an SSD is a binary decision: if you want faster load times, you add an SSD . . . if not, you don't.

    These builds are targeted at a fixed budget, and (at the moment, with these budgets) money should never be spent on an SSD at the expense of more cpu or graphics power.

    Dropping SSDs would also stop convoluting the "value" comparison.
    Reply
  • ethaniel
    82% performance at half the cost? 500 USD build for me, thanks. I can add a 100 bucks SSD anytime (and they'll just keep dropping). Newegg has some nice, cheap SSDs out there...
    Reply
  • tapher
    This has been a very informative triple build review, and this article sums up the lessons nicely! The point about the $1000 PC and games being fine with dual cores was gratifying to see echoed in the summation.

    The fact that problems were encountered during the builds, such as the issue with memory, and the issue with the bios; these are important practical lessons that make the articles well worth the time to read.

    Overall, I can't imagine a better choice of builds, nor a better outcome, given Sandy Bridge on the horizon.
    Reply
  • jestersage
    How about timing the marathon differently. It seemas doing it at the end of the quarter isn't such a good idea because of new tech launch schedules this half of the year. Maybe release the article in the middle of every quarter?

    In any case, the $500 build rocks my boat. I just feel it isn't right to saddle the $1000 build with a dual core, hyper-threaded or not. An AMD triple/quad core with bad-@ss cooling (at the same price) might have been better.
    Reply
  • Crashman
    canting_dissentorYour 'flexible' statistics are a joke! We'd really like the $2000 system to win to so we'll shovel in the hard drive figures with massive over-emphasis... It's bollocks.d00d, that's what a bunch of readers wanted. We all know that SSDs waste money for most users, but the site was overwhelmed by readers who claimed they couldn't wait for four seconds on a process that should open in three.
    Reply