Slashdot Mirror


Facebook VP Slams Intel's, AMD's Chip Performance Claims

narramissic writes "In an interview on stage at GigaOm's Structure conference in San Francisco on Thursday, Jonathan Heiliger, Facebook's VP of technical operations, told Om Malik that the latest generations of server processors from Intel and AMD don't deliver the performance gains that 'they're touting in the press.' 'And we're, literally in real time right now, trying to figure out why that is,' Heiliger said. He also had some harsh words for server makers: 'You guys don't get it,' Heiliger said. 'To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient.' Heiliger added that Google has done a great job designing and building its own servers for this kind of use."

370 comments

  1. You're Computin' for a Shootin' Mister by eldavojohn · · Score: 5, Insightful
    So let me get this straight, the Vice President of a web company is criticizing the hardware guys in two of the world's biggest chip makers?

    You guys don't get it

    Is it possible to take out a massive life insurance policy on Jonathan Heiliger?

    To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient.

    I assure you, despite your misconception that the world revolves around you everyone has those requirements. From the people who build supercomputers right down to the netbook I am typing on while watching Gurren Lagann.

    Can we get like a panel of hardware engineers to have a discussion with this guy and can I get some popcorn?

    --
    My work here is dung.
    1. Re:You're Computin' for a Shootin' Mister by Daengbo · · Score: 4, Informative

      Can we get like a panel of hardware engineers to have a discussion with this guy and can I get some popcorn?

      Slashdotters might want to take a look at the details of the Google servers to see what Heiliger is looking for. There's also a video tour.

    2. Re:You're Computin' for a Shootin' Mister by Frosty+Piss · · Score: 2, Insightful

      You've basically agreed with him. Whats your bitch? I don't get it.

      --
      If you want news from today, you have to come back tomorrow.
    3. Re:You're Computin' for a Shootin' Mister by timmarhy · · Score: 3, Insightful
      i don't know that i agree with some of googles design choices. do they account for details such as 10 small batteries are more expensive than 1 large battery of the same capacity?

      and why have a PSU for each unit, why not just run 12v power rails to each server and do the ac/dc conversion on a larger transformer further down the line with larger batteries providng the back up for clusters of servers? after all no psu is cheaper than a psu with just the 5v taken out.

      --
      If you mod me down, I will become more powerful than you can imagine....
    4. Re:You're Computin' for a Shootin' Mister by fuzzyfuzzyfungus · · Score: 4, Informative

      At low DC voltages, you can't really do long cable runs without either suffering substantial resistive losses or using cable so thick you could club a seal to death with it.

    5. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 5, Funny

      I vote for the seal clubbing thing.

    6. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      Thats what Blade Chassis are used for

    7. Re:You're Computin' for a Shootin' Mister by mabhatter654 · · Score: 3, Informative

      I think they run AC to the row or rack of servers, then they have just one super efficient PSU powering all the servers in a rack rather than 42 separate power supplies (plus UL enclosures, connectors, extension cords, etc, etc)

      Essentially Google builds "rack-sized" blade centers... or at least catching up to what IBM and HP are doing but on a bigger scale, like full racks or multiple racks managed at once rather than just one chassis.

      I do agree that chip makers aren't thinking "big enough" with things like their Blade lines.. Google wants to see reference specs that include options for bare motherboards to slide right into your basic 42 unit rack with IO, disk and power all pulled out to the raw basics so Google can decide how to manage the bits rather than having stock OEM boards with such limited options. Google wants to manage a "rack" as a single machine and optimize power and parts across 40 servers as one group, not 40 separate little systems.

    8. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      He did not "agree with him".

      The point is subtle:

      Yes, the requirements mentioned in the summary are ones that are important to everyone.
      No, Heiliger does not understand this, and seems to believe the requirements are specific to Facebook and Google-like sites.

      But: Yes, the hardware manufacturers are actually already aware of these requirements, but aren't meeting them.

    9. Re:You're Computin' for a Shootin' Mister by node+3 · · Score: 5, Funny

      i don't know that i agree with some of googles design choices

      I'm sure they'll get right on that, random slashdot guy...

    10. Re:You're Computin' for a Shootin' Mister by jamesh · · Score: 5, Funny

      cable so thick you could club a seal to death with it.

      What's with everyone creating new units of measure? "We're going to need some 3 Seal Cable for this job!"

    11. Re:You're Computin' for a Shootin' Mister by timmarhy · · Score: 1

      i wouldn't suggest one single psu for a whole center, just one per rack. surely it would be cheaper then messing around mounting batteries to each server? for one thing it'd make the racks top heavy if the rack wasn't 100% full.

      --
      If you mod me down, I will become more powerful than you can imagine....
    12. Re:You're Computin' for a Shootin' Mister by lukas84 · · Score: 2, Insightful

      Well, i can tell you that i do not want cheap, shitty hardware with no feature as servers.

      This is all fine for companies like Facebook and Google that are in the primary business of running IT, and wrote software that accomodates for the shitty hardware they use.

      However, other applications like standard business IT requires highly resilient, highly managable hardware which offers many features, stable parts supplies, management possibilites, and is built upon sturdy hardware that can withstand non-datacenter conditions of cooling and dust.

    13. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 5, Funny

      If we're gonna start the AC vs. DC war again, I call dibs on tasering the elephant this time.

    14. Re:You're Computin' for a Shootin' Mister by dasmoo · · Score: 1

      ATX power supplies are really, really cheap. Anything you build or buy to replace them is going to be more expensive than those mass produced parts. Saving power is about saving money, not about saving the environment. If power lost cost big dc power supply then they'll go with the cheaper option.

    15. Re:You're Computin' for a Shootin' Mister by KamuZ · · Score: 1

      Seriously people, April 1st as a date should tell you something is wrong... apart from the "innovative" designs.

      http://en.wikipedia.org/wiki/Google%27s_hoaxes#Oil_Tanker_Data_Center

    16. Re:You're Computin' for a Shootin' Mister by sigxcpu · · Score: 1

      if you look at the pictures of the google servers, you will see clearly that they have a standard AC power supply.

      --
      As of Postgres v6.2, time travel is no longer supported.
    17. Re:You're Computin' for a Shootin' Mister by gnick · · Score: 1

      3 cheers for the appropriate correction to the FP. Cheap and power-efficient are 2 of the variables that need to be evaluated when looking for a processor. The cheaper and more power efficient the better, of course. And, for Facebook, apparently those are the most important factors.

      However, for my home box I may be willing to spend 50% more power for a 40% speed gain, depending on what the baseline is. Also, I may be willing to drop an extra $100 for a 20% speed gain, again depending on the baseline. Also, since I'm running a single CPU, my multitasking needs are radically different than somebody like Facebook. And, since I'm doing multimedia and GUIs, my task needs are radically different than a processor meant to serve as a cell in a server farm. Even a single/dual CPU server has radically different needs than a huge server farm.

      Google/Facebook/Slashdot's needs are special because they're big. This should be a duh moment.

      --
      He's getting rather old, but he's a good mouse.
    18. Re:You're Computin' for a Shootin' Mister by node+3 · · Score: 0

      Why are you wearing purple trousers? (i.e., your question assumes something that isn't true)

    19. Re:You're Computin' for a Shootin' Mister by IntlHarvester · · Score: 1

      This is all fine for companies like Facebook and Google that are in the primary business of running IT, and wrote software that accomodates for the shitty hardware they use.

      That's the key point. Google wrote their own highly-scalable clustering software, but traditionally IT pays out the nose for clustering and it's cheaper to put the money into hardware.

      I don't see how Google/Facebook's requirements could be considered common in the slightest, but I suppose some ghetto sysadmin has dreams of running his enterprise off some loose Asus motherboards.

      --
      Business. Numbers. Money. People. Computer World.
    20. Re:You're Computin' for a Shootin' Mister by rcw-home · · Score: 4, Informative

      I think they run AC to the row or rack of servers, then they have just one super efficient PSU powering all the servers in a rack rather than 42 separate power supplies (plus UL enclosures, connectors, extension cords, etc, etc)

      No, they don't. They use motherboards built to their own specification that require only 12V power. This power is supplied by the server's own PSU, which takes 240V input. The PSU hooks into a 12V sealed lead acid battery, implementing UPS functionality (there is no centralized UPS).

      I think it's a very elegant design.

    21. Re:You're Computin' for a Shootin' Mister by timmarhy · · Score: 1

      i wear purple because i'm allergic to pink, you insensitive clod.

      --
      If you mod me down, I will become more powerful than you can imagine....
    22. Re:You're Computin' for a Shootin' Mister by TheLink · · Score: 1, Funny

      Talk about getting a seal of approval.

      --
    23. Re:You're Computin' for a Shootin' Mister by hairyfeet · · Score: 1

      If that is what he is looking for I wonder why he didn't look into Nano servers for his needs? Low power? Yep. Easy to cool? Yep. I don't know about the price but I bet buying in bulk like Facebook would do he would get a good price.

      It sounds to me like somebody didn't do his homework. As an added bonus the Nano has built in hardware crypto support which would help even more for things like HTTPS. He sounds like he would have been better off with Nano blades to me.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    24. Re:You're Computin' for a Shootin' Mister by pseudonomous · · Score: 5, Funny

      Oh, I finally get it now, Cat 5 cable can kill five cats, and cat 6 can kill SIX cats.

    25. Re:You're Computin' for a Shootin' Mister by Hecatonchires · · Score: 1

      coax was actually a japanese hyphenation of 'cow axe'. You had to use the axe on the cow, obviously. The vampire tap's were cool, but the server room always smelled of garlic.

      --

      Yay me!

    26. Re:You're Computin' for a Shootin' Mister by The+Archon+V2.0 · · Score: 1

      Oh, I finally get it now, Cat 5 cable can kill five cats, and cat 6 can kill SIX cats.

      Yup. But of course, that's only a guideline for typical cable lengths. With long cables, it doesn't quite work out like that. Take a 1000 ft. bulk box, for example; I can easily beat twice that many to death with one of those.

    27. Re:You're Computin' for a Shootin' Mister by Ihlosi · · Score: 5, Funny
      Oh, I finally get it now, Cat 5 cable can kill five cats, and cat 6 can kill SIX cats.

      But ... but ... you'll need Cat 9 to get rid of the cat completely?

    28. Re:You're Computin' for a Shootin' Mister by Freultwah · · Score: 1

      There is also the date of publication to be considered: April 1, 2009 2:26 PM PDT.

    29. Re:You're Computin' for a Shootin' Mister by TheLink · · Score: 0

      No need, there are cat 3 and cat 6 cables.

      --
    30. Re:You're Computin' for a Shootin' Mister by Lennie · · Score: 1

      elegant yeah maybe, but definitely more efficient.

      --
      New things are always on the horizon
    31. Re:You're Computin' for a Shootin' Mister by metacell · · Score: 2, Insightful

      So let me get this straight, the Vice President of a web company is criticizing the hardware guys in two of the world's biggest chip makers?

      He's not criticising their technical know-how, he's criticising them for not knowing what their web company customers want.

      Since he himself is one of those customers, it's not too unlikely that he knows what he's talking about.

    32. Re:You're Computin' for a Shootin' Mister by Jurily · · Score: 4, Insightful

      When you need the cheapest, most power-efficient servers you can find, to the point where you criticize your suppliers publicly, you're not willing to pay for the most expensive cables out there.

      Besides, all the seal clubbers are buying those up.

    33. Re:You're Computin' for a Shootin' Mister by metacell · · Score: 1

      I assure you, despite your misconception that the world revolves around you everyone has those requirements. From the people who build supercomputers right down to the netbook I am typing on while watching Gurren Lagann.

      No, not everyone has those requirements. A scientific workstation needs to have great multi-processor performance, at the expense of cost and power effiency. A computer embedded in a weapon needs to have solid reliabilty, at the expense of cost and sometimes, performance. A gaming desktop needs to have great performance, at the expense of cost and power effiency. A gaming laptop needs to have good performance and power-efficiency, at the expense of cost. And so on.

    34. Re:You're Computin' for a Shootin' Mister by TeknoHog · · Score: 1

      Or you can use it as a Cat o' 5 tails. Though it can actually have anything from 4 to 8 tails, depending on how you untwist the pairs.

      --
      Escher was the first MC and Giger invented the HR department.
    35. Re:You're Computin' for a Shootin' Mister by FreakyGreenLeaky · · Score: 1

      10 small batteries vs 1 large battery.
      Redundancy (well, not completely if all the batteries are acting as one, but at least if one takes a voltage dip, the whole thing won't stop working)? Let the bash-him-on-head-coz-he's-ignorant fest commence.

      why have a PSU for each unit
      Redundancy?

      larger transformer further down the line
      Single point of failure?

    36. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      Yes, then there is no cat.

    37. Re:You're Computin' for a Shootin' Mister by TheRaven64 · · Score: 2, Insightful

      Not to mention the fact that neither Google nor Facebook have important transactions. If, every million or so page accesses, one of their servers dies, who cares? The end user who has to hit refresh will probably blame it on their ISP.

      --
      I am TheRaven on Soylent News
    38. Re:You're Computin' for a Shootin' Mister by KibibyteBrain · · Score: 2, Insightful

      Yes, this reads like "Guy with huge ego upset that engineers can't use magic to conjure up ideal device at his command." to me.

    39. Re:You're Computin' for a Shootin' Mister by MonoSynth · · Score: 2, Funny

      But that will void your warranty!

    40. Re:You're Computin' for a Shootin' Mister by Antique+Geekmeister · · Score: 3, Informative

      You need a 'CAT5 of Nine Tails'. Google it: I've seen them made with usable sets of labeled connectors and adapters. on the ends to serve as an amusing collection of adapters, actually packed in a toolbox, and amusing as heck to whip out when a client had lost the appropriate adapter to go from their funky 3Com serial jack to normal laptop serial port, or needed a crossover cable to tie two machines directly together without a switch back in the pre-GigE days when network ports became hermaphroditic.

    41. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      Nah, just hit it twice!

    42. Re:You're Computin' for a Shootin' Mister by klubar · · Score: 1

      I have to agree... it depends what business you're in. For most commercial customers, reliability and support outweigh power or space savings. The additional support costs of data center designers, grid computing software and management quickly outweigh the nominal cost of additional power, AC and space.

      Unlike the poster who is willing to trade off for speed, I'd gladly trade 20-50% more space, power and heat for reliability and up-time.

      For the biggest datacenters that's probably not true--but they are probably large enough (or will to pay enough) to custom design hardware or have it custom built.

      True in a lot of industries--if you need small quanities you buy off the shelf hardware (and pay to have someone else design it), if it's core to your business you go custom.

    43. Re:You're Computin' for a Shootin' Mister by Leafheart · · Score: 1

      But ... but ... you'll need Cat 9 to get rid of the cat completely?

      The bdsm community might have something to talk to you about your cat o'9

      --
      --- "When you gotta do something wrong. You gotta do it right. (Fighter)"
    44. Re:You're Computin' for a Shootin' Mister by Late+Adopter · · Score: 1

      Sir, I would like to introduce you to the Mainframe.

    45. Re:You're Computin' for a Shootin' Mister by Fred+IV · · Score: 1

      Seals don't come with a warranty. Prepare the clubs!

    46. Re:You're Computin' for a Shootin' Mister by ceoyoyo · · Score: 1

      Cat o' nine.

    47. Re:You're Computin' for a Shootin' Mister by js_sebastian · · Score: 1

      When you need the cheapest, most power-efficient servers you can find, to the point where you criticize your suppliers publicly, you're not willing to pay for the most expensive cables out there.

      Besides, all the seal clubbers are buying those up.

      That's the real reason the EU is against seal clubbing...

    48. Re:You're Computin' for a Shootin' Mister by jmccay · · Score: 1

      I wonder if the VP bought multi-core technologies expecting that there would be an instantaneous improvement. The truth is that multi-core technologies don't guarantee massive improvements if the software was not written to take advantage of more than one processor. I think this is more a case of a VP seeing too much of the "big picture" and not enough of the details.

      --
      At the next eco-hypocrisy-meeting, count the private jets used to get to the meeting. Should be interesting to see that
    49. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      When you're company isn't pulling in the revenues you were expecting and you have a lot of investors to please, you'll find all sorts of people to blame for why you're not making billions in profit.

    50. Re:You're Computin' for a Shootin' Mister by Andy+Dodd · · Score: 1

      One thing I wonder:

      Many of the new CPUs DO have huge performance gains when running multimedia applications (video encoding/decoding, and especially 3D gaming).

      Maybe they just aren't as good for Facebook's systems, which probably don't do much floating point, if at all. Similarly, almost nothing FB does (except for possibly resizing images when they are uploaded by users) can take advantage of SIMD instructions such as SSE4 (which delivered huge performance gains for some relatively common desktop multimedia apps but isn't going to help an HTTP server or database server.)

      --
      retrorocket.o not found, launch anyway?
    51. Re:You're Computin' for a Shootin' Mister by fuzzyfuzzyfungus · · Score: 5, Funny

      Seals actually have an excellent warranty; but the sticker says "Warranty void if seal is broken" so the warranty has never been successfully claimed.

    52. Re:You're Computin' for a Shootin' Mister by Andy+Dodd · · Score: 2, Insightful

      "Google wants to see reference specs that include options for bare motherboards to slide right into your basic 42 unit rack with IO, disk and power all pulled out to the raw basics so Google can decide how to manage the bits rather than having stock OEM boards with such limited options."

      Sounds a lot like a VME backplane...

      --
      retrorocket.o not found, launch anyway?
    53. Re:You're Computin' for a Shootin' Mister by Andy+Dodd · · Score: 1

      Two lengths of Cat 5 is probably cheaper than one of Cat 3 and one of Cat 6, plus it's guaranteed to get the job done even if the cat has an extra life.

      --
      retrorocket.o not found, launch anyway?
    54. Re:You're Computin' for a Shootin' Mister by rgviza · · Score: 2, Insightful

      that guy is an ass.

      the latest generations of server processors from Intel and AMD don't deliver the performance gains that 'they're touting in the press

      then

      Google has done a great job designing and building its own servers for this kind of use

      I wonder who makes the server processors for Google's servers. Hmmm.....

      --
      Don't kid yourself. It's the size of the regexp AND how you use it that counts.
    55. Re:You're Computin' for a Shootin' Mister by Artuir · · Score: 1

      That explains why my cat chewed my 50' ethernet cable in half.

      Hmm..

    56. Re:You're Computin' for a Shootin' Mister by KillerBob · · Score: 2, Insightful

      Most battery UPS's upconvert the 12VDC to 120VAC to provide a standard power supply that you can plug anything into. That's because most of them run off standard boat or motorcycle 12V batteries which you can get at your local car parts store. Diesel or Gasoline UPS's are electric generators and usually cost a *lot* more. They make sense for keeping an office building powered, but not for keeping just a computer or thirty up. And that's above and beyond the power losses from transmitting 12V over a distance that you mention.

      I can see right away why it'd be cheaper to simply design a system to run off 12V directly and convert to 5V internally, and to having the battery right in that system.... first, you don't have to pay for the electronics in a UPS which convert the battery's 12VDC to 120VAC. Second, you don't lose energy in the form of heat, powering those electronics, and spinning the fans to keep it cool, and energy lost in transmission. A much higher proportion of the battery's power gets used to actually power the computer. The electronics which do the conversion from 12VDC to 5VDC are *much* cheaper, and less power intensive, than electronics that can increase the voltage, let alone converting it to alternating current.

      Think of it this way: it's basically a laptop, only without the keyboard, screen, video card, and with 8 memory slots and dual CPUs, and provisioning for two 3.5" hard drives. The system runs directly off the battery, and the power supply just charges the battery.

      Also, adding computers to the matrix doesn't reduce the length of time that you get from the UPS. I have a media center PC that's connected to a UPS, for example. The UPS is just running the computer and the sattelite receiver. In that configuration, it lasts about 1h without mains. If I were to plug the TV into it, it'd last about 25m. While you're operating on a *much* larger scale, the same would hold true for a centralized UPS. Each system you add reduces the overall effectiveness of the UPS by reducing the amount of time it can power the works without mains. By putting the battery directly on the server, you can add computers without diminishing this capacity. Your computing capacity in the event of power interruption scales up linearly, rather than hitting diminishing returns and a theoretical maximum limit.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    57. Re:You're Computin' for a Shootin' Mister by KillerBob · · Score: 1

      Well alright, but I wouldn't think that they'd enjoy techno or house....

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    58. Re:You're Computin' for a Shootin' Mister by buddyglass · · Score: 1

      There are integer SIMD ops as well, which can be useful for 128bit integer arithmetic and/or more efficient copying/swapping of memory.

    59. Re:You're Computin' for a Shootin' Mister by Dishevel · · Score: 1

      But that will void your warranty!

      And the Seals warranty as well!

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    60. Re:You're Computin' for a Shootin' Mister by Dishevel · · Score: 1

      I prefer no Tea

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    61. Re:You're Computin' for a Shootin' Mister by alexkraemer · · Score: 1

      Don't tase my elephant, bro!

    62. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      Like that ever stopped me from hacking a seal...

      (ducks...)

    63. Re:You're Computin' for a Shootin' Mister by TheNinjaroach · · Score: 1

      Yeah, and I've never been able to eat that box of animal crackers!

      --
      I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
    64. Re:You're Computin' for a Shootin' Mister by LeonPierre · · Score: 1

      Or two hits of Cat 5.
       

      --
      "If it ain't broke, it doesn't have enough features yet"
    65. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      if you had even bothered to READ ANYTHING about Google's set up you'd immediately realize a huge amount of gains came from doing the EXACT OPPOSITE of what you're claiming.

      i mean, fuck, man. shut your fucking mouth.

    66. Re:You're Computin' for a Shootin' Mister by n0tWorthy · · Score: 1

      Is that something like hocking a lugey?

      --
      "Be kind, for everyone you meet is facing a great battle." - Philo of Alexandria -
    67. Re:You're Computin' for a Shootin' Mister by Meest · · Score: 1

      So, if he's looking for this form of technology for their servers, why doesn't he just be like google and roll his own if he isn't happy with what the other offerings are? Is he just lazy and feels like complaining?

      If I can't find a solution to an issue I normally try and find my own solution instead of standing around complaining, as that will get me no where.

    68. Re:You're Computin' for a Shootin' Mister by DragonWriter · · Score: 2, Insightful

      So let me get this straight, the Vice President of a web company is criticizing the hardware guys in two of the world's biggest chip makers?

      Wrong.

      He is criticizing, in the bits in TFS, two groups:
      1) The marketing guys in two of the world's biggest chip makers (he's not complaining that the chips are flawed from an engineering perspective, he is complaining about the claims, which apparently conflict with Facebooks experience in testing them chips, about the performance of the chips), and
      2) The people setting the design goals (not, again, the engineers) at the companies making servers, complaining that they are doing a bad job of what he sees as a major need (which is, of course, also the particular thing that Facebook needs), and that Google does a better job of building servers for that need (a complaint which would be more effective at changing behavior at server manufacturers if it was followed up by Facebook going to Google to get Google to build them servers.)

      Can we get like a panel of hardware engineers to have a discussion with this guy and can I get some popcorn?

      Why? His complaints aren't directed at engineers.

    69. Re:You're Computin' for a Shootin' Mister by Anonymous+Cowpart · · Score: 1

      Sometimes, comments really, really deserve the (+6, coke on keyboard) mod...

    70. Re:You're Computin' for a Shootin' Mister by zapakh · · Score: 1

      If we're gonna start the AC vs. DC war again, I call dibs on tasering the elephant this time.

      You mean "Westinghousing the elephant"?

    71. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      >> Oh, I finally get it now, Cat 5 cable can kill five cats, and cat 6 can kill SIX cats.
      >
      > But ... but ... you'll need Cat 9 to get rid of the cat completely?

      No, you just have to hit it twice.

      Cat 5 does it in two hits, with one extra cat just to be
      sure. Cat 6 still takes two hits, and costs more. Lame.

    72. Re:You're Computin' for a Shootin' Mister by ArsonSmith · · Score: 1

      As proven by the Challenger explosion.

      Don't try to tell me it's too soon...

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    73. Re:You're Computin' for a Shootin' Mister by LackThereof · · Score: 1

      In the automotive industry, where they have been dealing with 12vdc power in long cable runs for a century, they have dealt with that by having the voltage regulator sense and adjust the voltage based on reading taken at the largest load, rather than at the source. Thus the voltage drop in long, thin cable runs is automatically compensated for. The alternator just puts out more voltage.

      --
      Legalize recreational marijuana. Seriously.
    74. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      i don't know that i agree with some of googles design choices. do they account for details such as 10 small batteries are more expensive than 1 large battery of the same capacity?

      Read the CNet article and comments; Yes they looked at other options like that. The thing you have to remember in centralizing anything is that now a failure can cause 40 machines to fail, rather than 1. So, you need redundancy, and more reliable parts, and a highly redundant systems for switching between the redundant systems. A lot of your cost advantage or average reliability then disappears. Now say you are running a serving on 4 racks of machines; Would you rather have a couple machines drop off every now and then, or (less freqently) a whole rack of machines? I know which I'd rather have happen, as losing 25% of one's resources at once a lot worse than something smoothed out over time.

      and why have a PSU for each unit, why not just run 12v power rails to each server and do the ac/dc conversion on a larger transformer further down the line with larger batteries providng the back up for clusters of servers? after all no psu is cheaper than a psu with just the 5v taken out.

      The same argument I made above applies here. At my work we have had a power failure in one of our very large "uninterruptable" power supplies, twice, in 3 months. What failed was a (redundant) CPU controlling a very complex UPS/flywheel/generator combo -- such a failure should not cause a problem, but it did. We paid for reliability, instead we are getting a rebate; we'd rather have had the reliability. Around the same time, the CNet story came out about google's locally batery-backed machines, and the argument was both timely and compelling. Hopefully server manufacturers pick up the idea. It sounds like facebook would buy them in numbers at least.

    75. Re:You're Computin' for a Shootin' Mister by AmberBlackCat · · Score: 1

      I've heard enough "hardware engineers" criticizing "software engineers" that I don't care if a software guy criticizes hardware guys for a while. Neither is really qualified to judge the other.

    76. Re:You're Computin' for a Shootin' Mister by nomel · · Score: 1

      At low DC voltages, you can't really do long cable runs without either suffering substantial resistive losses or using cable so thick you could club a seal to death with it.

      Your statement is completely wrong, and I assume you're a troll.

      Lower voltages means higher current for the same amount of power (P=I*V).

      The power loss for a resistive cable is P=(I^2)*R. So, as current increases, power loss increases dramatically!

      And, this power is converted to heat, so, you must increase the thickness of the cable!

      This is why we use 300,000V and higher for power transmission lines, to minimize the current flowing through the wire, minimizing the power lost due to the resistance of that wire. And, that's why obscene amounts of power can fly through those relatively thin cables.

    77. Re:You're Computin' for a Shootin' Mister by nomel · · Score: 1

      Oops...forgot to put why they do it that way...because one AC to DC power converter can be made to run much more efficiently than many AC to DC converters handling a fraction of the power.

      If you look at the efficiency curve of a converter, it starts out at 0, rise steeply to near peak, rolls up to peak, then start to fall down a bit. Somewhat idle PC's use very little power, giving the least efficiency! So, if you have an overpopulated server farm (to handle spikes) then, most of your pc's will be idle...burning much more power than they should. So, they use one massive power converter that handles much more power, but is always running at/near the peak of the efficiency curve during "average" loads.

      And, then you use big fat rails (think thick pipes) as a power bus to negate the increased resistive losses, as mentioned in the last post.

    78. Re:You're Computin' for a Shootin' Mister by nomel · · Score: 1

      Still, there should be a big efficiency using a mains converter that brings it down to 12 rather than many smaller supplies that bring it from line voltage to 12 and lower.

    79. Re:You're Computin' for a Shootin' Mister by nomel · · Score: 1

      Proof of this being
      "We were able to measure our actual usage to greater than 99.9 percent efficiency." when converting the power from the battery to the mobo.

    80. Re:You're Computin' for a Shootin' Mister by madseal · · Score: 0

      "I do agree that chip makers aren't thinking "big enough" with things like their Blade lines.. "

      That's not a chip maker issue, that's more of a system supplier. The chips themselves are efficient, but what Google does, and what it would take to make these efficient farms is more of an issue with system design. He should be complaining to the HP's, IBM's, Sun Microsystems people of this world. Or like was pointed out, design your own blade server to supply your needs...

    81. Re:You're Computin' for a Shootin' Mister by rcw-home · · Score: 1

      Still, there should be a big efficiency using a mains converter that brings it down to 12 rather than many smaller supplies that bring it from line voltage to 12 and lower.

      Not really. Remember the 99.9% efficiency number you read is only the power supply's efficiency on battery. It's not the power supply's efficiency when on AC power and it's not the motherboard's power regulation efficiency. Google's setup is better than most, perhaps even optimal, but I'd be very surprised if the chips and hard drives received more than 80% of the power drawn from the power cord.

      Most of their gains are from avoiding an extra AC->DC->AC conversion from a centralized UPS. A typical server has its power converted like this:

      • AC Line Power
      • DC UPS batteries
      • AC UPS Inverter
      • DC Power Supply Rectification
      • AC (High Frequency) Power Supply Inverter
      • AC (High Frequency) Transformer
      • DC Power Supply Output Rectification
      • AC Motherboard Voltage Regulator Inverter
      • DC Motherboard Voltage Regulator Rectifier

      Note that additional separate voltages are parallel paths in the last half of this chain - not additional steps in it. Google's setup has a few less steps:

      • AC Line Power
      • DC Power Supply Rectification
      • AC (High Frequency) Power Supply Inverter
      • AC (High Frequency) Transformer
      • DC Power Supply Output Rectification (Battery hookup)
      • AC Motherboard Voltage Regulator Inverter
      • DC Motherboard Voltage Regulator Rectifier

      Google just realized that the motherboard has its own power supply on it anyway, so why not make it official and have it do the final voltage regulation. The bulk of the 12V power gets converted to very low voltages, so there's no reason why the buck regulator that accepts that 12V power can't accept a fairly wide voltage range from a battery.

    82. Re:You're Computin' for a Shootin' Mister by mabhatter654 · · Score: 1

      ha! I can type comments with mouth closed! :|

    83. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      The battery doesn't surprise me. It's similar to the NetApp NVRAM mindset.

    84. Re:You're Computin' for a Shootin' Mister by lsatenstein · · Score: 0

      Actually, the VP is right. And the problem is the architecture. 64bit AMD/Intel architecture is very adequate for the desktop, but not for servers. Their microcode does not pipeline enough, and the dma needs to transfer 128bytes at a time, not just the 64bits at a time. Also, need the disk system bios to really be a subsystem, part of a disk controller, not part of the main bios. Offload work where possible, or switch to Mainframe systems which give more bang for the buck.

      --
      Leslie Satenstein Montreal Quebec Canada
    85. Re:You're Computin' for a Shootin' Mister by Anonymous Coward · · Score: 0

      That's a bit like overkill.

  2. WTF? by Spit · · Score: 1, Insightful

    Maybe the dude should have benchmarked before committing. How does he scope his projects, with brochures?

    --
    POKE 36879,8
    1. Re:WTF? by Zebai · · Score: 5, Insightful

      I agree I think this was writing his own resignation with this crap. The guy is basically telling everyone that he is incapable of finding an acceptable solution for his company and blaming intel and amd because he has committed a great deal of money on something that he didn't plan well enough to know exactly what the long term costs vs performance was. In the very article he says to not be cheap, but in many more words than necessary, probably to try to disguise what he is saying like most politicians, that they were not only too cheap, but made bad decisions on what to be cheap with. Its as if he's already in a public office, hes telling everyone he screwed up, why he screwed up, and trying to make it look like hes teaching everyone lesson to make his mistake to be less of a disaster.

    2. Re:WTF? by Spit · · Score: 4, Interesting

      Looks like that to me; he scoped for cheap and cheerful and was bit on the ass when he realised that sometimes you get what you pay for. Like what's the point in having quad-core server CPU without the high-bandwidth buses of server-grade hardware.

      In the concurrent DNS/Kaminsky thread, I saw a reference that facebook's DNS TTL is low. A quick investigation reveals that they have a 30 second TTL and are using DNS round-robin for their load balancing.

      He's nothing but a blame-shifting cretin.

      --
      POKE 36879,8
    3. Re:WTF? by whoever57 · · Score: 1, Informative

      I have some sympathy for this guy. Some years ago, I built a fileserver using the best SATA RAID (hardware RAID) cards I could find (~$300) from major manufacturers and enterprise disks (specified for use in RAID systems)

      Performance absolutely sucked. The cards were fast enough it I tried to read/write single large files, but when reading/writing large numbers of small files, they were very slow. The first manufacturer's card was appallingly slow. I replaced it with another manufacturer's card and performance was merely slow.

      I followed all the manufacturer's recommendations, I communicated with one manufacturer on a Linux RAID mailing list, but was never able to get anything remotely like acceptable performance. For compariso, later I built a fileserver around an old (sub 1GHz) PC, using software RAID and was able to get at least the same performance.

      I was only building one machine, so I did not have the luxury of benchmarking it.

      --
      The real "Libtards" are the Libertarians!
    4. Re:WTF? by cryogenix · · Score: 4, Insightful

      I think we read different articles. He's not saying he didn't plan well enough, he's saying that Intel and AMD promise that Gen Y processor is 35% faster than Gen X processor, and he's not seeing anywhere near 35% in real world performance. The 35% is a made up number but it doesn't matter what the number is that they claim. He's probably correct. Manufacturers pull this stuff all the time. Look at the recent articles on battery life claims on notebook's. AMD came out and called BS on the whole thing and basically said if you guys don't stop lying through your teeth, the FTC is going to regulate us. From the perspective you are taking, that would mean we have to call AMD incompetent for not understanding how batteries work and not properly selecting them.

      Manufacturers ALWAYS overstate claims in computer related products. CRT actual inches vs viewable inches (thank you lcd's for finally being honest... about inches anyway.. brightness and contrast however....) Computer speaker wattage being 1/2 or 1/4 of what's claimed. Power supply efficiency or wattage not measuring up to claims... you name it. He's calling out what he see's to be bogus claims based on a real world experiences in a demanding environment, the type of environment where one is always looking for better performance. I think we should get some more information before declaring him to be the problem as I'm sure he has a whole team of people that are working on this issue.

      What I'd like to see from him is some numbers. On this Intel (or AMD) rig, we get so many operations per hour/minute/whatever. On this new Intel (or AMD) rig which they claim is 20% faster than the previous rig, we're only seeing this number of operations per hour which amounts to only a 7% gain, thus we're seeing 13% less than they are claiming. Again, numbers made up for examples sake. I'd also be very interested in what a typical rig of theirs looks like... X Processor, Y Ram, what type of storage system is it connected to, etc. I think such numbers are vital to understanding the issues at hand. We all know that vendors will run the benchmarks that makes their stuff look the best, and that is often not reflective of real world performance. If I was Intel/AMD I'd be chiming in right about now and opening a dialog with Facebook and looking to see what the issues are. Facebook is a big customer with huge name recognition and you want to be able to use them as an example of your solution delivering the promised performance for your marketing. I'm going to assume (I know I know) that they are already working with the server vendor to try and see what's going on here.

    5. Re:WTF? by afidel · · Score: 1, Insightful

      Wow, you found out that 7200rpm SATA disks suck for small random I/O? That's surely a shocker! Oh wait, it's not and the least bit of research would tell you that. It's the same thing with Facebook, they expect to get awesome performance/dollar out of interpreted code and are blaming the hardware when it doesn't magically come true.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    6. Re:WTF? by MidnightBrewer · · Score: 2, Interesting

      How can you be blamed for finding an acceptable solution when there simply isn't one available? He is a software developer, not a hardware one. Not everybody can just go out and design their own servers like Google does. He's saying he's been tripped up by the fact that the server manufacturers aren't delivering on their promises; hardly something he should be blamed for. Your attempts to read more into his comment about "not being cheap" and compare it to the false words of a politician seems like a pretty big stretch.

      If you read the entire article, he not only doesn't say that his decisions have led to disasters, but instead says that his infrastructure development decisions have led to very smooth transitions, even when Facebook rolls out big, new features like the customized home page URLs. He is only voicing his disappointment in saying that the servers aren't living up to the hype, and that he is still looking for a better solution.

      I will say that his comment to not be cheap seems to be in direct conflict with the rest of his argument, since his criticism over AMD and Intel revolves around the fact that they need to be cheaper. Seems a bit counter-intuitive.

      --
      "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life
    7. Re:WTF? by Spit · · Score: 2, Interesting

      You can better identify your bottlenecks by benchmarking. Facebook's scalability is likely not as cpu-bound as predicted, thus the dude's angst on discovering that CPU upgrades weren't a silver bullet.

      In your case, you haven't looked past the RAID configuration for the root-cause of your performance issues. Without benchmarking you don't really know if it was an issue with: the filesystem, the block size, stripe size, or a caching tunable.

      Systems architecture isn't as easy as PC builders would have you believe.

      --
      POKE 36879,8
    8. Re:WTF? by Anonymous Coward · · Score: 1, Informative

      It may be the proc's themselves are performing close to the advertised improvements (not sure where 35% improvement comes from for both Intel and AMD), its just that bottlenecks elsewhere are stopping that being seen.

      For example, if memory bandwidth is important watch out for the Nehalem memory clockrate dropoff...
      http://blog.scottlowe.org/2009/05/11/introduction-to-nehalem-memory/

      BTW, the recent Opteron/Xeon improvements are mostly around number of cores in one socket at the same/similar clock speed and same power use so IF the code multithreads well, then it should see most of those gains.

      So if performance isn't adequate, should you buy more since the app scales so well? :^)

      I call BS too ...

    9. Re:WTF? by lukas84 · · Score: 1

      You used slow SATA Disks and complain about low IOPS when doing random IO?

      You'll be sure to get a job at Facebook :)

    10. Re:WTF? by edmudama · · Score: 5, Insightful

      I think we read different articles. He's not saying he didn't plan well enough, he's saying that Intel and AMD promise that Gen Y processor is 35% faster than Gen X processor, and he's not seeing anywhere near 35% in real world performance.

      If the application was purely CPU bound, and Y wasn't giving me 35% more than X, I'd complain.

      However, if it's a complex system like almost everything else, why would they expect their application to get 35% faster when there's probably 6 or 8 critical subsystems that could all be bottlenecks as well?

      --
      More data, damnit!
    11. Re:WTF? by macshit · · Score: 1

      I've no idea what Intel/AMD claimed, but you'd have to be utterly naive to believe any claim involving a single fixed performance increase. Modern systems are very complex, and performance is insanely context dependent. Facebook's server apps are not going to be precisely like anybody else's apps, and there's simply no way to know how they'll perform without testing them.

      ...and of course you wouldn't expect somebody with the title "VP of technical operations" to be so technically naive ...
      oh... wait. Facebook.

      Never mind.

      --
      We live, as we dream -- alone....
    12. Re:WTF? by Anonymous Coward · · Score: 1, Informative

      agreed and make sure your OS is tuned/setup for rapid I/O ... http://en.wikipedia.org/wiki/Anticipatory_scheduling or the 2.6 standard http://en.wikipedia.org/wiki/CFQ. Maybe the system was using the deadline scheduler on an old 2.6 or 2.4 branch.

      Facebook might need OS and Network engineering skills internally to optimize their server hardware/software setups. Seems like they've got performance issues at every level and are trying to cram in a bigger CPU hoping it will scale with the problem.

    13. Re:WTF? by Runaway1956 · · Score: 3, Interesting

      Uhhh, correct me if I'm wrong. I've been looking at after market bolt on parts for my car. The headers claim increase fuel mileage, the spark plugs, the air filter, the tires, as does a turbocharger. The glass pack mufflers, and the resonator. Oh yeah, the aerodynamic rims, the hood, and spoiler. Don't forget the carbon fiber body panels. Taken all together, those increased MPG's add up to about 150 MPG. You're saying I may not see that much improvement on my 1968 Chevy Malibu? It's just hype? Man - you just saved me about $5,000!!!

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    14. Re:WTF? by cryogenix · · Score: 1

      Hence my request for more specifics.

    15. Re:WTF? by cryogenix · · Score: 1

      What a waste of money, you could have gotten one of those things you plug into your cigarette lighter and gotten similar results ;)

    16. Re:WTF? by cryogenix · · Score: 1

      I think you're doing a bit of guilt by association. The IT guys running the back end are not necessarily the ones that do code design, or corporate direction such as what new bone headed feature to add into Facebook that will annoy all of the users today. I'd suspect they are like a lot of companies where they are just tasked with making it work. You can't scale to something of Facebook's size without knowing a bit about what you are doing. Don't lump the techs in with the policy makers.

    17. Re:WTF? by Anonymous Coward · · Score: 1, Interesting

      At the end of your long comment u said "If I was Intel/AMD I'd be chiming in right about now and opening a dialog with Facebook and looking to see what the issues are. Facebook is a big customer with huge name recognition and you want to be able to use them as an example of your solution delivering the promised performance for your marketing."

      U know the funny thing is...back in the day, lets say Pentium 1, 2 and 3 days. AMD had awesome products, and no one was buying because they had no idea who these guys were. (Example. AMD was first to make 1 GHz CPU and it was faster per clock then Intel's offerings). So what AMD did is they went out of their way to work with customers, to get sales, and they slowly built up a name for themselves...its really funny that after they reached the top (remember athlon VS Pentium when AMD was without a doubt better), they "forget" to do the things that got them where they are, and wonder why they are dieing.

    18. Re:WTF? by Hecatonchires · · Score: 1

      Or "lets buy sata drawers. They're heaps cheaper and larger than fibre drawers" Cheap, Fast, Good. Pick two. (Low Cost, High Performance, High quality)

      --

      Yay me!

    19. Re:WTF? by Hecatonchires · · Score: 1

      +1 Use of a car example

      --

      Yay me!

    20. Re:WTF? by Shaiku · · Score: 1

      So my take was that he's a total choad. He's blaming the chip makers for his software's poor performance and his company's inability to design a scalable architecture? If he is so damn sure of what he wants, then why isn't he putting it together himself? He blames the server manufacturers for failing to provide both super fast and ultra low-power machines. He spec'd the whole thing out of Unobtanium and then complained that *surprise* nobody can deliver it. Maybe his app is I/O or memory bound, and a 35% increase in CPU performance isn't going to do shit. Maybe he should have purchased a couple new CPUs and tested them before committing to a large purchase and then pointing his finger at the marketing reps. He says servers have to be powerful, power efficient, and cheap. Then he says his advice is "don't be cheap." What a choad-farmer. I'll bet he bitches that his wife isn't Smart, Beautiful, AND Sane. He doesn't seem to get the concept of "You have three options: pick two." That's my two cents--keep the change.

    21. Re:WTF? by rainer_d · · Score: 1

      I think we read different articles. He's not saying he didn't plan well enough, he's saying that Intel and AMD promise that Gen Y processor is 35% faster than Gen X processor, and he's not seeing anywhere near 35% in real world performance.

      So his fault is that he actually believed a vendor.
      Does he also belief in the tooth-fairy?

      --
      Windows 2000 - from the guys who brought us edlin
    22. Re:WTF? by amorsen · · Score: 2, Interesting

      No, he just found that RAID controllers suck. Which they do, universally, all the time. The only ones that actually perform decently are the ones in external SAN boxes, and inside they are typically servers with software RAID...

      --
      Finally! A year of moderation! Ready for 2019?
    23. Re:WTF? by TheRaven64 · · Score: 4, Interesting

      One of the fun toys Intel has to play with is a complete system simulator, which simulates every single component in a computer for early testing. This lets them vary parameters that aren't feasible yet while they're working on their design goals. A few years ago they did a test; what happens to the system performance if you make the CPU infinitely fast? They adjusted the simulator so that every CPU operation took zero simulated time and ran their benchmark suite. It ran twice as fast (in simulated time) as it was before.

      A CPU-bound workload can quickly become a RAM-speed bound or a disk-speed bound workload if you make the CPU faster but don't upgrade anything else.

      --
      I am TheRaven on Soylent News
    24. Re:WTF? by somenickname · · Score: 1

      Actually, if the application is purely CPU bound and well tuned for CPU X, then switching to the superior CPU Y may not give you an performance benefits at all until it's recompiled and possibly tuned for CPU Y. That assumes the compilers have been updated to understand how to optimally schedule instructions for CPU Y, what new instructions may be available on CPU Y, etc. Hardware vendors know these things whereas hardware consumers think that CPU Y is supposed to be faster and so their software should be running faster.

      An example of this was when Sun was switching from UltraSPARC II to UltraSPARC III. Even though the UltraSPARC III chips were clocked 50% higher and had all sorts of goodies that made it seem like a better chip, when the first internal machines appeared performance was dismal and was often below UltraSPARC II in benchmarks. Once the compilers became smart enough to emit optimized code for the UltraSPARC III and once the systems engineers doing benchmarking understood the quirks of the new CPU, performance started to get more inline with expectations.

    25. Re:WTF? by lukas84 · · Score: 1

      Yeah, but the guy complaining here isn't a tech, he's a policy maker.

      If the rich snobs fuck up, they blame Intel and AMD. Because really, why would they admit they made a mistake?

    26. Re:WTF? by ezzzD55J · · Score: 1

      his company's inability to design a scalable architecture?

      You don't know what facebook is, do you?

    27. Re:WTF? by GaryOlson · · Score: 1

      Now spend that savings on a few classes in critical thinking and analysis....if the government will let you.

      --
      Every mans' island needs an ocean; choose your ocean carefully.
    28. Re:WTF? by cryogenix · · Score: 1

      I have a poster of that in my office... the cheap/fast/good triangle :) A lot of vendors like Lefthand however like the whole tray of sata drives... It's not bad for things like file servers for mid range companies.

    29. Re:WTF? by cryogenix · · Score: 1

      So you're of the opinion that if something doesn't meet up with claimed performance gains, obviously the purchaser is at fault and it's not possible that the manufacturer overstated claims at all? Or worse, you're saying that if you actually believed a vendor, you're an idiot? If you aren't seeing the benefits claimed, you should just what, shut up and not say anything? I don't agree with that. I don't think you do either and I'm probably oversimplifying your argument, but that's how it breaks down when I look at it. I think if you're in a position to throw some weight around as a company that size is, you go ahead and speak up and call a spade a spade. It may come down to something Facebook is doing wrong, in which case that guy will be eating a lot of crow, but if in fact, there's some overstating going on, and we know there often is, it's in the best interest of everyone if people step up and call them on it. I'll cite the AMD example again. We all know batter claims are BS, so why should we continue to put up with it? The answer is, we shouldn't, but what you or I say on a comment board, even slashdot, isn't really going to make a difference to your hp's and lenovo's and dell's, because none of them are willing to make a realistic adjustment to their numbers unless they are sure the others will follow, otherwise hey they are suddenly getting a lot less run time than everyone else. It takes a company such as AMD to put it out there on the table to get attention. I think he has some very valid arguments there. Again, specifics and numbers would really help that article, but take a look at google. They basically have the same opinion which is why they build their own units. There's a lot of debate as to if that's a great idea to do or not, but I think google won that debate because they do it and it works. Perhaps Facebook is going to need to go a similar route if server vendors aren't going to deliver what they want. We're all sitting here nitpicking the words of a company that actually runs a huge operation whereas I'd be willing to be bet most of the people here replying (myself included) have never operated anything on a scale that they are talking about. I think we're going to have to wait and see, but I'm hoping there's some follow up articles that detail this out more as I'd like to see the ultimate outcome.

    30. Re:WTF? by Anonymous Coward · · Score: 0

      It's like the twitters, ain't it?

    31. Re:WTF? by maraist · · Score: 1

      "If the application was purely CPU bound, and Y wasn't giving me 35% more than X, I'd complain."

      Huh? Why should a specific APP be expected to achieve that max theoretical performance increase that a contrived benchmark (specInt, etc) rates? While this class of bench marks is based on 'real world apps', nobody uses those apps anymore.

      You can write two 'CPU bound' apps that have completely different branch-patterns and memory-patterns. One with great instruction-sequentially and mem-locality (and thus deep-pipeline utilization and highly cacheable even though it exceeds the cache size) and one which makes effectively random walks through memory with contingent random code-jumps (such that DRAM banks are constantly powered up and down). You'll totally trash the memory performance and thus your memory bus bandwidth is bumpkiss.

      So if you are currently achieving say 60% max-theoretical throughput on CPU-1, then what the author is suggesting is that CPU-2 should achieve 135% * (60% * CPU-1). But the design decisions of the new CPU might be such that the particular code-flow of the target app are actually WORSE (i.e. a longer pipeline visa v. the Pentium 4). The issue might be more subtle, such as fooling the branch-predictor logic (which is complex). Or it could be that the data-dependent random memory walks are such that the parallel memory channels CAN'T be utilized effectively. So BW and parallel chips don't make up for fundamentally rate-limited random-access latency.

      The point is, ALWAYS sample the new hardware and make mass purchasing choices based on your personal cost-benefit analysis.. Bitching to the vendor is unfruitful - choose alternate purchasing strategies.

      --
      -Michael
    32. Re:WTF? by surgen · · Score: 1

      >He's saying he's been tripped up by the fact that the server manufacturers aren't delivering on their promises; hardly something he should be blamed for.

      Only if Intel/AMD used facebook's software for their benchmarks could he expect the same sort of performance increase for facebook's software. He believed that their statistics on performance gain would translate directly for his software, and he can be blamed for that.

    33. Re:WTF? by lukas84 · · Score: 1

      So you're of the opinion that if something doesn't meet up with claimed performance gains, obviously the purchaser is at fault and it's not possible that the manufacturer overstated claims at all?

      If Intel claims that performance with new Xeons 5500 improved 35% in their benchmark X, and it doesn't then they'd have a case.

      But they aren't running benchmarks - they're running their applications, in which they (obviously) aren't getting a 35% speed improvement.

      Or worse, you're saying that if you actually believed a vendor, you're an idiot?

      It depends. If you're talking to an Intel sales, which claims that their new 5500 Xeons will improve performance by 200% for half the energy usage for Facebook's specific use cases, and the guy as a technical executive believes this bullshit, then yes - it's mostly his fault.

    34. Re:WTF? by Anonymous Coward · · Score: 0

      Probably, but what's so bad about that load balancing technique? AFAICS, assuming fairly constant traffic it should work about as well as anything else at minimal cost.

    35. Re:WTF? by buddyglass · · Score: 1

      It doesn't seem obvious to me from the article that he bought a gillion processors and is now disappointed with their performance. He just says that one of the unexpected barriers they've run into in their quest to continually upgrade their infrastructure performance is the fact that Intel & AMD's server CPUs don't live up to their marketing when it comes to Facebook's particular workload. Given that he also touts "testing" as a key to success in the very same article, I'm assuming they tested the performance of next-gen processors before buying a ton of them.

    36. Re:WTF? by MikeBabcock · · Score: 1

      ... at the cost of the increased DNS traffic both for clients and his servers.

      --
      - Michael T. Babcock (Yes, I blog)
    37. Re:WTF? by ITJC68 · · Score: 1

      Excellent post. From someone who obviously read the article and understood what the complaint was. I too believe that Intel and AMD stretch what their "new and improved" CPUs deliver. It is the same in the desktop arena. Dual core versus Quad core. People buy the cheapest quad thinking they will be better off versus the faster (GHZ) dual core. Until the market can make good utilization of dual cores for the desktop (they are but not enough to warrant 3 or 4 cores) it is pointless. I always use Toms Hardware for real world comparison and it has always been a very good resource.

    38. Re:WTF? by bored · · Score: 1

      No, he just found that RAID controllers suck. Which they do, universally, all the time. The only ones that actually perform decently are the ones in external SAN boxes, and inside they are typically servers with software RAID...

      Mostly, right, except that if by "software" you mean software which drives big honking DMA and parity/Galois field computation engines in hardware, or runs on microcontrollers designed for the task, then yes.. PPC 440SPE

    39. Re:WTF? by AmberBlackCat · · Score: 1

      And if you accuse them of lying about the performance increase, or accuse them of being unable to produce a 150mpg car, you're right.

    40. Re:WTF? by Anonymous Coward · · Score: 0

      Run XP on a new Core2Duo system. Using his logic, it should be twice as fast if not faster than XP on a single core P4 from 2006. It isn't. Why? XP was not built to use two cores efficiently, as is the case with most software on the market today.

      Software plays a huge role in hardware speeds. Poorly written software even more so.

    41. Re:WTF? by cstdenis · · Score: 1

      Until mainstream web browsers are ready to use something else for HA and load balancing like PTR or NAPTR, dns round robin is about all we have.

      --
      1984 was not supposed to be an instruction manual.
    42. Re:WTF? by MikeBabcock · · Score: 1

      There's nothing stopping you from using geo-information based mirroring or multiple hosts behind proxy servers doing invisible round-robin without low-ttl DNS issues.

      --
      - Michael T. Babcock (Yes, I blog)
  3. Hm... by Darkness404 · · Score: 3, Insightful

    To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient.

    Hm, lets see... perhaps because Facebook and Amazon are niche markets? The average server isn't going to even need all the computing horsepower and the power efficiency is simply a drop in the bucket for most companies electrical bills. The average server is going to be much more I/O intensive than CPU intensive unless you do cluster computing or render a lot of stuff. The average server such as a web server or a file server doesn't use that much CPU and usually you are running 1-3 servers, not the hundreds that Facebook or Amazon would run.

    And really, why is a VP complaining about this stuff? That he can't either afford custom solutions or spend the money buying more servers?

    --
    Taxation is legalized theft, no more, no less.
    1. Re:Hm... by VinylRecords · · Score: 0, Troll

      Hm, lets see... perhaps because Facebook and Amazon are niche markets?

      Niche market? Considering over 100 million people are logging into Facebook every day and Amazon is massive online retail entity I would hardly call them niche.

      Some info on Facebook:
      - More than 200 million active users
      - More than 100 million users log on to Facebook at least once each day

      http://www.facebook.com/press/info.php?statistics
      http://www.alexa.com/topsites

      Facebook is the fourth most popular website according to Alexa and Amazon is at 34. Niche? Really?

    2. Re:Hm... by Darkness404 · · Score: 2, Insightful

      Niche as in, only a few companies (~100) are going to need the same solutions. On the other hand the vast majority of servers will be for much, much, much less intense use. Then you have the problem that really Facebook isn't super profitable, Amazon is but they seem to be doing decent with their servers and have the spare cash to simply upgrade them. I mean, other than a few websites who needs a "perfect" server?

      --
      Taxation is legalized theft, no more, no less.
    3. Re:Hm... by JackieBrown · · Score: 0, Redundant

      You need to read his post again if you think that is what darkness meant

    4. Re:Hm... by Quothz · · Score: 2, Informative

      Hm, lets see... perhaps because Facebook and Amazon are niche markets?

      -Maybe-. Even if they are a niche market, they're a big enough one to hold the attention of the big chipmakers.

      A traditional business model might use large orders, especially advance orders, to offset or defray the cost of setting up a production line or facility, and get most of the profit from smaller sales. Or they may choose only to do production runs for large, inherently profitable orders. Even in a firing-from-the-hip model, large customers cost less per unit in marketing and sales than do smaller ones, very much so when compared to the general public. And of course there's plenty of wiggle room between extremes. So depending on the diversity of the market and the choice of business model, big customers range from important to desirable. Naturally, in a niche market large customers have a greater importance, since smaller sales are fewer.

      Presumably, AMD and Intel are selling servers to the likes of Amazon and Facebook 'cause they think it's profitable. If it is a niche market, keeping those guys happy is paramount to profitability.

      (I don't think the server farm market is really a niche, tho'. But I dunno; I don't keep up with such things.)

      And really, why is a VP complaining about this stuff? That he can't either afford custom solutions or spend the money buying more servers?

      Well, because we asked. Well, not "we" as such, but someone asked him and he answered. It sounds like he was answering honestly and openly. I've no problem with that.

    5. Re:Hm... by vux984 · · Score: 1

      That he can't either afford custom solutions or spend the money buying more servers?

      Tell me again what Facebook's revenue model is...??

    6. Re:Hm... by HockeyPuck · · Score: 5, Informative

      The average server is going to be much more I/O intensive than CPU intensive unless you do cluster computing or render a lot of stuff.

      As someone who designs and deploys large storage environments for a living, I call BS. While the current generation of HBAs are 8Gb FibreChannel, I would say that the "average server" (as you put it) could happily live on a 1Gb HBA. Recall that almost all servers, or atleast those you care about, have DUAL HBA connections to their respective storage. So that's actually 2Gb of storage connectivity. Sure there are servers which have multiple HBAs, or use a higher utilization of the HBAs, such as database servers or backup/media servers. Most servers today are deployed with dual 4Gb HBAs as the 8Gb SFPs/optics are still quite pricey, and you cannot, in all seriousness, purchase 1 or 2Gb FC HBAs.

      Even as we deploy VMware based servers, the VMware servers themselves tend to be more memory/cpu strapped than IO.

      It would be very rare, or almost impossible for a server to be driving linerate HBAs, with still plenty of headroom left in the CPU. Even basic test tools like IOmeter require significant CPU usage to drive an HBA to capacity. And that is when it's writing/reading all zeros. It's doesn't actually need to do anything with the data. As would be the case if a database server was requesting 2Gb/s from a disk array, and then had to join/sort/add/whatever the tables retrieved.

       

    7. Re:Hm... by Anonymous Coward · · Score: 0

      I assume the masses of PHP scripts they have to run aren't CPU intensive? And rather large SQL databases...

    8. Re:Hm... by mabhatter654 · · Score: 1

      they may be "niche" but data centers are the top multiple unit customers, buying thousands of the exact same configurations from OEMS .... they've surpassed the "enterprise cube farm" desktops buy a good margin in that data centers buy the MOST expensive server CPU they can where Enterprises are buying the cheapest desktops they can... Data center customers and Gamers are the only ones that NEED new CPUS every six months... nobody else really cares as they're out buying no-profit Atom based netbooks now.

    9. Re:Hm... by Anonymous Coward · · Score: 0

      Well, because we asked. Well, not "we" as such, but someone asked him and he answered. It sounds like he was answering honestly and openly. I've no problem with that.

      Nice business plan -- trash the only two outfits who can get you what you want.

      Flies, honey, vinegar.

    10. Re:Hm... by lukas84 · · Score: 1

      A good way for small VMware deployments i've found to be using e.G. a NetApp filer and run the VMs over NFS. Much cheaper than a real SAN, and more flexible, while still retaining the same performance.

      I'm not sure if NFS is a good idea in bigger deployments, though.

    11. Re:Hm... by Anonymous Coward · · Score: 0

      because when you are writing zeros, the zeros are not being copied from one device, or memory to another.

      So writing zeros is more cpu intensive than writing random data that is already in memory.

      If the data is already available in memory, or on a block device the cpu will issue a DMA request, and the memory controller/north bridge will complete the
      copy task without loading any data into the cpu registers. When the data is done copying, the dma controller will generate a hardware interrupt.

      The same thing can happen over the network, with tcp offloading cards, and rdma: http://www.rdmaconsortium.org/home

    12. Re:Hm... by Mozk · · Score: 1

      Secretly selling all the data it accumulates on its users?

      --
      No existe.
    13. Re:Hm... by tyrione · · Score: 1

      To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient.

      Hm, lets see... perhaps because Facebook and Amazon are niche markets? The average server isn't going to even need all the computing horsepower and the power efficiency is simply a drop in the bucket for most companies electrical bills. The average server is going to be much more I/O intensive than CPU intensive unless you do cluster computing or render a lot of stuff. The average server such as a web server or a file server doesn't use that much CPU and usually you are running 1-3 servers, not the hundreds that Facebook or Amazon would run. And really, why is a VP complaining about this stuff? That he can't either afford custom solutions or spend the money buying more servers?

      Agreed. Imagine this guy deploying regional Telco solutions. Facebook doesn't touch the level of tiering required for what people bitch about regarding their 3G options. Enterprise Data Centers, Call Center Suites, etc., are massive and when we really start moving everything to parallel blocks of code he might want to look at the architecture of the actual software.

    14. Re:Hm... by drsmithy · · Score: 2, Informative

      As someone who designs and deploys large storage environments for a living,

      Then you should know that throughput is not the only (or - typically - the most important) measure of IO performance.

      Typical computing tasks tend to be I/O bound - specifically by random I/O performance. To a large degree, this is due to the massive disparity in performance improvements between CPUa and storage.

    15. Re:Hm... by Anonymous Coward · · Score: 0

      Seriously, you do this for a living? Is it a very good living?

          You may have a limited range of experience, perhaps specialized. In any case, I can tell you that it is not grounded in current technology limits. The 'average server' doesn't use FibreChannel at all. Simple SAS or SATA storage is the standard. A small server (1U) may have a 6-disk array, pumping out perhaps 650 MB/sec or more of sequential throughput, for both reading and writing. In your terms, that is over "5Gb".

          "HBA" is really typically a FibreChannel term, which again is not even a factor in the common server.

          A larger server might have larger arrays, or a couple of RAID controllers. This can easily push the aggregate bandwith over 1GB/sec (or 8Gb, in awkward terms). There are some limits at the higher ends, of course.

          Driving this full bandwidth requires minimal CPU, when properly configured. "Properly configured" does involve a decent RAID controller, with substantial battery-backed RAM, good drivers, a good filesystem choice, and decent configuration of all. And, any common server today is going to have a minimum of 8 cores anyway.

          Custom processing pipelines can do significant work and drive the bulk of that bandwidth. A database will likely be far suboptimal - partially because of overhead in the work being done, and partially because they appear to just not be caught up to modern hardware. Still, even PostgreSQL can blow past your 1Gb, handily.

          Random access times also can come into play. These are still I/O.

          Basically, there are many common cases where even a database will have low CPU usage and minimal benefit from adding memory. What do you think it is bottlenecked on, in such cases?

    16. Re:Hm... by Anonymous Coward · · Score: 0

      NSA domestic spying programs don't need a revenue model. It's called taxes. Why try to build a mind-reading machine when you can do the next-best thing? People are only too happy to dump their entire lives into Facebook, where the NSA mines the data for otherwise obscure relationships. When you disappear suddenly, no one will ask where you went. They will know the answer, but will be too terrified to verbalize it. If you follow this one rule, though, you can avoid winding up in a Wackenhut gulag: Dissent is only patriotic if it's not directed at our dear mullah Obama, peace be upon him.

    17. Re:Hm... by ezzzD55J · · Score: 2, Insightful

      Kindof depends on how you read 'niche.' yes, there is a relatively small number of companies (customers) that have such requirements, but if each of them have a massive, massive number of servers, then i wouldn't call that niche any more, because it still represents a large turnover.

    18. Re:Hm... by ezzzD55J · · Score: 1

      Tell me again what Facebook's revenue model is...??

      i can't answer that very well, but i know they have a lot of money.

    19. Re:Hm... by arethuza · · Score: 1

      He did say "designs and deploys large storage environments for a living" - certainly in normal (i.e. not Google or Facebook) data center environments servers will have either FC connections to a SAN if they are doing anything serious or iSCSI for stuff that needs to be on the SAN but doesn't need FC performance. YMMV.

    20. Re:Hm... by MightyDrunken · · Score: 1

      Even basic test tools like IOmeter require significant CPU usage to drive an HBA to capacity. And that is when it's writing/reading all zeros. It's doesn't actually need to do anything with the data. As would be the case if a database server was requesting 2Gb/s from a disk array, and then had to join/sort/add/whatever the tables retrieved.

      What is the CPU doing? Is the memory controller/CPU overwhelmed with data? With say 1Gb of I/O how does the seek time affect the performance of the work these servers are doing?

    21. Re:Hm... by Anonymous Coward · · Score: 0

      the obvious conclusion is that your hbas + vmware are not
      an efficient combination.

      i get linerate AoE on 2gbe nics at 5% cpu on some pretty
      pitiful linux machines.

    22. Re:Hm... by Anonymous Coward · · Score: 0

      Maybe he meant that the average server spends most of its time waiting for the mechanical heads of the hard disks to deliver requested data instead of worrying that it can't process more than 100 MB/s of data. ie limited by IO-ops/s instead of bandwidth
      Most disk access is random especially for servers running multiple virtual machines.

    23. Re:Hm... by Anonymous Coward · · Score: 0

      I would disagree, for anything built with an understanding of modern hardware and costs. I have built more than one cluster for storing and processing hundreds of terabytes of data. This includes distributed database operation, custom processing pipelines, and a distributed computation framework. These are not in Google or Facebook.

          This can be done for low cost, and with high performance and efficiency. Involving a SAN blows that away. For a SAN, the cost is extreme, and the performance won't come close to the aggregate performance of local storage. There are specialized cases where a SAN is still useful, but they are actually increasingly not any large storage environments. A large storage environment implies that you need a sizable number of nodes anyway.

          Unless "large storage environment" here means "10 TB", and a lack of engineering expertise to support anything but the most hands-off solution. Then, sure, wire a handful of machines into a SAN. Be ready to accept the cruddy performance mentioned above.

    24. Re:Hm... by Anonymous Coward · · Score: 0

      You may have a point, but I'm going to pick on your example.

      Even as we deploy VMware based servers, the VMware servers themselves tend to be more memory/cpu strapped than IO.

      The whole POINT of consolidating servers into a virtual environment is to increase memory/cpu utilization of the host. I would think they are not "average" servers at this point.

      +1 Used IT professional acronyms that 95% of /. "Nerds" couldn't point out in a lineup.

  4. YouTube... by Anonymous Coward · · Score: 0

    YouTube has been constantly crashing and showing server errors more frequently over the last month. I'm not sure how much more bandwidth that YouTube demands over Facebook or Amazon (if it does) but whatever issues with servers and reliability that the Facebook team is having with Intel and AMD might be even worse over at YouTube.

    Anyone experiencing major outages and slow movement and loading times over at YouTube recently? Can't say I've had a problem with Amazon or Facebook other than intended outages for updates or repairs in the last month.

    1. Re:YouTube... by Mozk · · Score: 1

      I'm not sure how much more bandwidth that YouTube demands over Facebook or Amazon (if it does) [...]

      Two years ago, it was reported that YouTube accounted 20% of all HTTP traffic and 10% of all Internet traffic, and I can't imagine that its popularity would have waned since then.

      So, yeah, it does.

      --
      No existe.
  5. Facebook's application is poorly coded by jsimon12 · · Score: 3, Insightful

    I have heard from some reliable sources that Facebook and Twitter's backend applications are poorly written.

    Are Intel and AMD's claims overblown, sure what hardware manufacter doesn't cherry pick performance claims.

    But I don't care what sort of hardware you through at crap code you are always going to get crap performance.

    1. Re:Facebook's application is poorly coded by lothos · · Score: 1

      The facebook code was leaked a year ago:

        Facebook users on Monday were left contemplating the security of private details stored on the social-networking site after part of its source code was leaked onto the Internet.

      The site on Monday acknowledged that a section of its code had been copied and published on a blog, but stressed that none of the personal details of its 52 million users had been compromised.

      Over the weekend, a blog called Facebook Secrets published details of part of Facebook's source code, the set of commands which determine the way the site appears when it is viewed by users.

    2. Re:Facebook's application is poorly coded by royallthefourth · · Score: 3, Insightful

      Crap code on faster computer is still going to be faster than it was on a slower computer. He's not saying anything about how efficient their software is, just that buying new processors didn't get him the performance delta that it was supposed to. More advanced hardware should deliver a performance benefit no matter what is running on it.

    3. Re:Facebook's application is poorly coded by corychristison · · Score: 2, Insightful

      More advanced hardware should deliver a performance benefit no matter what is running on it.

      Not if your code is not tuned for this new "advanced hardware". Surely there are new compile flags to consider, and if you are not tuning your code for the new processor features it could very well be slower than before.

    4. Re:Facebook's application is poorly coded by evanbd · · Score: 3, Insightful

      Developers have been known to trade off performance for development ease. Frequently the result is crap code. Yes, it performs like crap on both sets of processors. But if the application is CPU-limited (rather than IO or memory or...), then throwing faster CPUs at it ought to make it proportionally faster, no? Obviously they thought the previous performance was acceptable, is it unreasonable to think that buying CPUs marketed as 50% faster should give a 50% performance increase? Clearly crap code will still run like crap, but you ought to be able to throw more CPU power at it and get 150% of crap performance.

    5. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Crap code on faster computer is still going to be faster than it was on a slower computer

      That is only partially true. But what if they have algs in there that are O(N^N)? Say N is the number of users? And they are adding 1000 new users per day?

      So as they add more users the 'better' hardware does NOTHING for them. It sounds like Intel or AMD reps promised them the moon and they bought the story. I would say perhaps he was sold a bill of goods. But guess what without metrics to back it up. Like how does it run with HIS software I would say he didnt do his job.

      I would also say a bad alg on better hardware will eventually perform just as bad once you add more users. They are trying to throw more hardware at the problem without understanding the problem. Or perhaps they do but are unwilling/unable to change something?

    6. Re:Facebook's application is poorly coded by royallthefourth · · Score: 1

      More advanced hardware should deliver a performance benefit no matter what is running on it.

      Not if your code is not tuned for this new "advanced hardware". Surely there are new compile flags to consider, and if you are not tuning your code for the new processor features it could very well be slower than before.

      Facebook is written in PHP; there are no compile flags.

    7. Re:Facebook's application is poorly coded by hidden · · Score: 5, Informative

      Facebook is written in PHP; there are no compile flags.

      apache and the php engine have plenty of compile flags. not to mention whatever the database is.

    8. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Ya don't think, maybe this makes compile flags even more important for the base PHP lib?

    9. Re:Facebook's application is poorly coded by Necroman · · Score: 4, Interesting

      One of the server techs from Twitter was at SXSW 2 years and gave some details about how their backend servers worked. If I remember correctly (there were 4 sites on the panel, so I may be confusing them with someone else), the original code was written in Ruby on Rails which did not scale well to the multi-server systems that they had setup. They have spent a lot of time improving their code over the years, but from what I could tell, their initial implementation wasn't the most thought out thing in the world.

      --
      Its not what it is, its something else.
    10. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      ...

      But I don't care what sort of hardware you through at crap code you are always going to get crap performance.

      A wise man once said: A computer's performance is 10% hardware, 90% software

    11. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Developers have been known to trade off performance for development ease.

      [cough] java [cough]

    12. Re:Facebook's application is poorly coded by Cloudwalking · · Score: 1

      Furthermore, while the front-end is PHP, there's all kinds of custom (non-PHP) stuff running in the back. Here's a neat post about the PHP though: http://blog.facebook.com/blog.php?post=2356432130

    13. Re:Facebook's application is poorly coded by dbcad7 · · Score: 1

      I suppose that is true to a point.. but perhaps there is more to the story than processors.. for example, I imagine you would have similar experiences in surfing the internet when comparing the latest processor and something 5 years old .. when they are both connected using a 300 baud modem.. A faster processor doesn't necessarily mean a faster "system".. and software is part of that system.. mp3's don't play faster with a faster processor (by design) perhaps there is something in the design of their software that is limiting the performance.

      --
      waiting for ad.doubleclick.net
    14. Re:Facebook's application is poorly coded by lena_10326 · · Score: 1

      You're joking right?

      I hope so because network IO is the major bottleneck on the majority of webservers, not raw processing. You could write insanely inefficient code with all compiler optimization flags turned off and the timing difference would still be nothing compared to the network latencies with the database or internal/external web service calls. The second bottleneck is generally disk IO.

      --
      Camping on quad since 1996.
    15. Re:Facebook's application is poorly coded by lukas84 · · Score: 1

      I'm quite sure that an IBM DS8000 stuffed to the brim with SSD's will alleviate most of the hard drive bottleneck issues ;)

    16. Re:Facebook's application is poorly coded by Stormie · · Score: 4, Interesting

      I have heard from some reliable sources that Facebook and Twitter's backend applications are poorly written.

      Given the quality of Facebook's developer API (it's horrible), I'd be amazed if the back-end of the actual site wasn't poorly written.

    17. Re:Facebook's application is poorly coded by Bill,+Shooter+of+Bul · · Score: 1

      Twitter went from pure ruby on rails, to some ruby messaging class, to a scala written one. The first two were awful, haven't looked too much at the last one. Facebook seems more reliable, and has dealt with its ever increasing userbase pretty well. They seem to use sensible parts including hadoop. They just recently hired away Mysql guru Mark Callaghan from Google. Not sure what they're doing with mysql, but I was never sure what Google did with it either.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    18. Re:Facebook's application is poorly coded by f0dder · · Score: 1

      Unless the bottle neck isn't in the cpu, probably a combination of I/O + expensive database queries. Mebbe they need to get halal drives for for those AMD !slamic machines.

    19. Re:Facebook's application is poorly coded by Samah · · Score: 2, Insightful

      Facebook is written in PHP

      There's your problem right there... ;)

      --
      Homonyms are fun!
      You're driving your car, but they're riding their bikes there.
    20. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      I program a lot as a hobby. I have made/ am making games that are thousands of lines of code long. I may not have a PHD in programming nor do i claim to be the authority on programming but i know this. The difference between a well written program and a poorly written program is night and day. The actually performance may easily vary by a factor of 2, 10 or 100. The latest and greatest cpu will give say a 20% performance increase...So if it is poorly written...the real thing to be looking at is fixing up the program.

      So i have to completely agree with the statement

      "But I don't care what sort of hardware you through at crap code you are always going to get crap performance."

    21. Re:Facebook's application is poorly coded by Mozk · · Score: 1

      It was only the home.php code, so I wouldn't call it Facebook's source code. It wasn't part of the backend; it was mostly code that included other code.

      --
      No existe.
    22. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Question marks. Have you heard of them?

    23. Re:Facebook's application is poorly coded by timeOday · · Score: 1

      Not if your code is not tuned for this new "advanced hardware". Surely there are new compile flags to consider, and if you are not tuning your code for the new processor features it could very well be slower than before.

      Then it isn't much of an upgrade. The CPU market thrived from its inception until just a few years ago because regular upgrades were justified by predictable performance increases. We went from about 7 mhz to about 3000 mhz in about 20 years, and it was great, the so-called "mhz myth" notwithstanding.

    24. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Crap code on faster computer is still going to be faster than it was on a slower computer. He's not saying anything about how efficient their software is, just that buying new processors didn't get him the performance delta that it was supposed to. More advanced hardware should deliver a performance benefit no matter what is running on it.

      Garbage in, garbage out.

    25. Re:Facebook's application is poorly coded by grantek · · Score: 1

      Not necessarily - for example, if you look at the PC boot sequence, people have been screaming that there are too many hard-coded sleep periods that don't get smaller as processors get faster. It's feasible there's similar locking problems (especially if it's associated with I/O) in a web app.

    26. Re:Facebook's application is poorly coded by cenc · · Score: 1

      This totally has my vote.

      Fuck the CPU. It is the least of the problems with any system server or otherwise today. Go beat the mobo producers, not the CPU producers. Essentially our disks are no faster than they where 3 years ago, or even 5 years ago, but their capacity has gone through the roof (minor catch improvements aside). We have more data to move in to and out of disk. If you can't get it in to the disk any faster or out of the disk any faster, what the hell is the point of a fast processor or more processors?

      So, we find ourselves shoving more and more data in ram, caches to caches, because the disks are so friken slow.

    27. Re:Facebook's application is poorly coded by cowbutt · · Score: 4, Informative
      Essentially our disks are no faster than they where 3 years ago, or even 5 years ago

      # hdparm -Tt /dev/sdc

      /dev/sdc:
      Timing cached reads: 5120 MB in 2.00 seconds = 2562.04 MB/sec
      Timing buffered disk reads: 84 MB in 3.02 seconds = 27.77 MB/sec # hdparm -i /dev/sdc | grep Model
      Model=ST3200822A, FwRev=3.01, SerialNo=xxxxxx
      # hdparm -Tt /dev/sda

      /dev/sda:
      Timing cached reads: 6078 MB in 1.99 seconds = 3052.95 MB/sec
      Timing buffered disk reads: 338 MB in 3.01 seconds = 112.22 MB/sec
      # hdparm -i /dev/sda | grep Model
      Model=ST31000333AS, FwRev=SD1B, SerialNo=xxxxxx

      It's not even a full order of magnitude faster, but 112MB/s is still nearly four times faster. And these are both magnetic discs, rather than SSDs.

    28. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      They also use C++ for their backend services. It's on their software dev job postings.

    29. Re:Facebook's application is poorly coded by tyrione · · Score: 1

      Your math skills are crap.

    30. Re:Facebook's application is poorly coded by gbjbaanb · · Score: 2, Insightful

      throwing proportionally faster CPUs at *good* code should make it proportionally faster.

      Crap code.... probably not. For example, I once had to improve the performance of an app. The app spent most of its time context switching from one thread to another, more time was taken up stopping a thread, switching to another, refilling the cache lines, and so on that was spent processing the data! Think what a faster processor would do here - the CPU would process the little bit of data it was given faster thus providing much more CPU time for context switching.

      Similarly with other aspects of modern code - relatively little of it is spent spinning CPU cycles. I'd say more was spent dealing with memory IO (as there is a lot of RAM used nowadays, getting that data to and from the CPU is, relatively speaking, slow as treacle) so it wouldn't matter if you could crunch the data faster if you still had to wait for it to be delivered to you.

      Then we put more stuff on the network, and connect to it via Web services and the like, and the amount of CPU power required gets less and less relevant.

      I'd say the single best thing you can do to get good performance, and therefore energy efficiency, and cheapness of resources is to write efficient code that requires little resources itself. Even if it takes you longer to do the job, tough on you - there's just you as a programmer but millions of users, the extra time spent developing at a lower level (instead of pointy-clicking in the IDE) is time well spent.

      If Facebook's code could be made 10% more efficient, they'd require 10% less servers with all the reduced energy bill that entails. But the Facebook chap doesn't care about that - that'd cost him programmer time, and that costs short-term money! Far better for him to whinge that Intel and AMD aren't fixing his shit for him instead.

    31. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Facebook and Twitter are/were written with languages whose implementations are so inefficient that they probably cache miss so much trawling through hash tables that the memory hierarchy obliterates the CPU's performance. Twitter has moved some of its implementation onto Scala, which is certainly less inefficient than CRuby at everything. Whether either of these host applications that do anything that benefits from superscalar CPUs with aggressive OOE is another matter. It is quite possible for an application to waste vast amounts of the utilized silicon because they simply aren't congruent.

      If Facebook wants to bankroll a processor architecture like Sun's T1, Intel might be interested, but since it cannot be repurposed for desktop use like their present microarchitecture what would be the incentive for them to do it themselves and sell them for Xeon prices? That's how Intel outsold vendors with different architectures: companies like Facebook went with commodity hardware to cut upfront costs and the expensive UNIX vendors with custom hardware dropped off like flies.

    32. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 2, Insightful

      Not "unreasonable", but possibly naive and inexperienced, depending on the details.

      Crap code that bottlenecks a CPU often will not scale as well as good code. It involved bad synchronization, other contention, spinning loops, and memory bandwidth limits. It is often NUMA-unfriendly. It often interacts poorly with the other resources, such as I/O.

    33. Re:Facebook's application is poorly coded by jjgm · · Score: 2, Informative

      That may be so. The new drive may indeed have four times the raw read throughput. But how much larger are they? Five times.

      And even more tellingly, look at the seek performance. I looked up those two drives you mentioned. You'll find it's unchanged at 8.5ms. So we're seeking at the same speed, for more data.

      In practice, then, in terms of throughput per provisioned GB, we are 24% worse off, and in terms of seek time per megabyte we are TEN times worse off today!

      To illustrate what I mean, based on those numbers above: slurping 10TB off an idealised JBOD array of those newer drives would take 89 seconds; slurping 10TB off an idealised array of the older drives in parallel would take only 72 seconds. A similar (but far worse) story applies to random seek time performance, especially for busy transaction systems.

      One might challenge the exact figures, but it doesn't matter - the point is, drive size is an important gotcha in storage performance optimisation today, and it's because performance has not really kept pace with drive size. The issue is not offset by the bigger caches they're turning up with, although that helps for some workloads.

      We haven't talked dollars. The cost is important, but that's another dimension. Let's keep this to engineering chatter.

      So what happens in shops that need really high performance? Well, if it's an application with lots of random reads but with hotspots, then cache will do nicely. But for raw random write performance i.e. the heavy transaction processing applications, it's gotta be more 15K RPM spindles at lower capacity. Or go crazy and solid state, but that's another party.

    34. Re:Facebook's application is poorly coded by hattig · · Score: 1

      Well CPUs process data.

      If the data can't be provided quickly enough, then all that will happen is that the faster CPU will process what it gets quicker, and then have a nap waiting for some more.

      I'm sure Facebook has multiple replicated databases in order to handle the load, and I'm sure that the servers have tonnes of RAM in order to cache information in user sessions to reduce load on the database... Yes? I'm sure they're not using SOAP/XML for internal messaging, but using a binary protocol like Google's protocol buffers, but above that doing all they can to reduce network I/O, such as keeping each user session on the same front-end webserver, etc.

      See, Google's system works because Google hires good software engineers who solve problems so that their internal networks can cope.

    35. Re:Facebook's application is poorly coded by Big_Mamma · · Score: 1

      This really makes me doubt their ability to benchmark / scale things properly. In the article, he sounds like facebook is completely CPU bound, and yet he's slamming the latest generation server processors by Intel / AMD?

      From all the benchmarks I've seen, like Anandtech's and from personal experience, web servers scale pretty much linearly with clock speed * IPC and the amount of cores present in the system. The addition of HT is good for another 20% throughput.

      What they need to do is to look at their setup, and make sure there isn't another bottleneck - have you spawned enough threads and processes to utilize the system completely? PHP may be "thread safe", but that usually means that there's a huge lock around everything that could be dangerous and one process refuses to use more than 100% cpu on 1 core, so serve it with apache-prefork + load balancer + separate static file server. Same thing for Python - fork off more copies via mod_wsgi even in threaded mode, as many as you can afford within the available RAM, or the Global Interpreter Lock will limit the CPU usage to 1 core.

      If you have setup the environment well and there are no other bottlenecks, web services scale perfectly with the available CPU power. And that has increased by an insane amount for the Xeon 54xx to 55xx, it's almost doubled the performance in most server apps (OLTP, VM), but even the PHP test case which failed to scale to 16 cores in a single process was good for +39%.

    36. Re:Facebook's application is poorly coded by cowbutt · · Score: 1

      We haven't talked dollars. The cost is important, but that's another dimension. Let's keep this to engineering chatter.

      So what happens in shops that need really high performance? Well, if it's an application with lots of random reads but with hotspots, then cache will do nicely. But for raw random write performance i.e. the heavy transaction processing applications, it's gotta be more 15K RPM spindles at lower capacity. Or go crazy and solid state, but that's another party.

      But the cost is part of the system engineering; I paid £77 each for the 200GB models in Nov 2004, and £88 each for the 1TB models in Dec 2008. That's pretty much the same price allowing for four years of inflation in between. So using RAID (or wider RAIDs if you were already using RAID) is even more affordable. I've been using RAID on my main home system since 2002. If you needed to use a 5*200GB JBOD in 2004, you should be able to justify at least a 8*1TB RAID10 array by now, or, as you say, upgrading from bog-standard 7200RPM drives to something faster; 10K, 15K or SSD.

      Sure, from an engineering standpoint, it'd be elegant if there were fundamental and radical improvements (analogous to architectural improvements in CPU design), but from a pragmatic standpoint, who cares if you can get something fast enough by throwing more drives at the problem (analogous to ramping up the clock speed in CPU design).

    37. Re:Facebook's application is poorly coded by jjgm · · Score: 1

      Unfortunately, enterprises tend to pre-purchase shared storage and buying 8TB of disk when you only need 1TB of space tends to get you noticed during economic downturns.

      There will always be a market need for small, fast drives, and to bring this back to the original guy's point - it's because by some very practical considerations, several performance metrics per raw TB have actually declined.

    38. Re:Facebook's application is poorly coded by ceoyoyo · · Score: 1

      And we all know how much better it is when the crap is flying faster.

      Sure, a faster processor will make your crap code go faster, but there are all sorts of reasons why it won't make it go as fast as the CPU manufacturer's specs.

      Where I'm at right now instead of linking libraries they have a bunch of little utilities that all perform fairly basic tasks on large datasets. In order to build up a complex algorithm you have to chain together a bunch of these utilities, with LOTS of disk, or at least cache, writes in between.

      A faster CPU makes a difference, but not much unless you throw in a faster disk as well.

    39. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      No, depends on where the bottleneck is. If it's in Memory or I/O no amount of CPU speed increase will help.

      Also it's entirely possible Facebook is growing beyond rational means. There is a limit to technology today, and it's not a matter of not trying hard enough to invent faster computers, it's just what are tech is capable of.

      Maybe if Facebook's home page didn't have 3 million images, apps, and other random fucking annoying popups they'd have a lower hit.

    40. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Thats a sequential test? You're an idiot. Try a random/semi random test; try some tests which are actually simulating a real life workload w/ and w/out memory cache.

      Disk performance -hasn't- changed across the board. The linear IO throughput has changed but there's plenty of usage cases where that doesn't give you anything.

      (Posting AC to not karma whore.)

    41. Re:Facebook's application is poorly coded by cowbutt · · Score: 1

      Thats a sequential test? You're an idiot. Try a random/semi random test; try some tests which are actually simulating a real life workload w/ and w/out memory cache.

      Disk performance -hasn't- changed across the board. The linear IO throughput has changed but there's plenty of usage cases where that doesn't give you anything.

      The OP said "Essentially our disks are no faster than they where 3 years ago, or even 5 years ago". Even a sequential test between a current drive and a five year old drive proves that statement false.

      Of course, what you say is more precise, and correct, but we also have affordable and mass-market SSD devices. If it's low latency and fast "seek" times you're after, then that's the way to go, today. Some may say that's comparing apples and oranges, but when you start hitting the physical limitations of a device design, I'd say it's time to start looking at different designs that provide the same function.

    42. Re:Facebook's application is poorly coded by MikeBabcock · · Score: 1

      My new hard drives are substantially faster than the ones I bought a few years ago. The ones from a few years ago were also substantially faster than those before that.

      Buy yourself an SATA2 drive with NCQ and a computer that supports it, make sure its at least 7200RPM with a nice 8MB cache and tell me its not faster than a similar drive from say 3 years ago.

      --
      - Michael T. Babcock (Yes, I blog)
    43. Re:Facebook's application is poorly coded by MikeBabcock · · Score: 1

      I've seen crap code that doesn't improve much with better hardware. Things like:

      for i in blah.length()
      {
          data += blah
          f.write(data)
          while (f.writing()) sleep(500)
      }

      As another example, I was reading the driver code for a PCI serial device I have and it loops through all 128 ports looking for waiting data then rests and does it again and ignores the hardware interrupts.

      --
      - Michael T. Babcock (Yes, I blog)
    44. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      That's only for a contiguous block of data though. Random seek times haven't improved much.

    45. Re:Facebook's application is poorly coded by Blakey+Rat · · Score: 1

      Has there ever been a runaway popular software product that wasn't poorly-written? At least initially?

      Coin it as "Blakeyrat's Law."

    46. Re:Facebook's application is poorly coded by RightSaidFred99 · · Score: 1

      It will probably, but want to bet they're using normal and possibly even commodity hard drives?

    47. Re:Facebook's application is poorly coded by _avs_007 · · Score: 1

      So you're saying if I write (for example) an applicaiton to use only a single thread, and use blocking calls for all my I/O operations, I can expect huge performance benefits from migrating to better hardware? You can put in an 8 core system, it won't help your single threaded application if it's using blocking I/O calls.

    48. Re:Facebook's application is poorly coded by relguj9 · · Score: 1

      is it unreasonable to think that buying CPUs marketed as 50% faster should give a 50% performance increase?

      Yes, it is unreasonable, entirely. Even if the CPU is the only physical bottleneck, you still can't expect X% clock speed to correlate to X% performance increase. That's pretty basic computer/software engineering. You can make reasonable estimations, but the only way to know what your gains will be is to test it.

      Anymore, 35% faster can mean any number of things as well, it's not just straight speed of operation execution. 35% faster could mean that they increased the efficiency of some operations, bumped up the 1st level cache, increased clock speed or any combination of those plus other things. The 35% is probably just an attempt to put all of the gains into a single number that really can't be presumed to be all that accurate.

      Basically, you'd need to know exactly what was changed or upgraded from your previous CPU and figure out how each of those upgrades will affect your particular configuration before making any reasonable estimation of performance gains. It would be absolutely impossible for AMD or Intel to do this for you.

    49. Re:Facebook's application is poorly coded by evanbd · · Score: 1

      You'll note I said 50% faster, not 50% higher clock speed. He's complaining about benchmark numbers, which you may have noticed are not the same thing as clock speed.

    50. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      Crap code usually does not scale linearly.

    51. Re:Facebook's application is poorly coded by Anonymous Coward · · Score: 0

      28MB/s is far too slow for a five year old disk, either there is something wrong with it (that is slowing it down) or you are running it over USB.

      I have a 5 year old Hitachi Deskstar that gets ~60MB/s in hdparm.

      So effectively spinning disks are only nearly twice as fast, and that only for sequential reads, not random data access.

  6. Well I suppose... by cptnapalm · · Score: 3, Funny

    Well, I suppose that if he does not like the offerings from Intel and AMD, they could always go with...

    Uh..

    Oh.

    1. Re:Well I suppose... by the+linux+geek · · Score: 5, Informative

      Let's see... IBM, Sun, Fujitsu, Itanium (yeah, its still Intel, but has great performance)... All of these can offer equivalent or much better performance at these kinds of applications than what they're using. Don't bitch if you're not willing to consider the alternatives.

    2. Re:Well I suppose... by WilliamBaughman · · Score: 1

      Well, Sun's Niagara 2 processor seems pretty good at number of network I/O operations per Watt. And if he doesn't like that, he can try IBM's Power6, although I hear it's better for floating-point than integer (relative to Intel and AMD's offerings.) If he doesn't like that, he can sell his company to Google and ask them to build servers for him.

    3. Re:Well I suppose... by NervousNerd · · Score: 1

      I heard that Cyrix CPU's had bitching performance.

    4. Re:Well I suppose... by WilliamBaughman · · Score: 1

      [...] Itanium (yeah, its still Intel, but has great performance) [...]

      Does a VLIW processor with lots of cache really do well (in terms of transactions per Watt) compared to a non-VLIW processor for hosting web apps? My understanding was that Itanium chips were made on older processes because of their large die size, they need the lowest possible defect rate to get good yields. That hurts their performance / power. Also, I don't know if having a large amount of cache is cost effective for hosting web apps unless you're hosting the same content again and again, at least compared to having lots of RAM and fast memory access. Using power and transistors on cache doesn't seem like a good idea to me when you're serving that much data for random access requests. Also, I don't see how Instruction level parallelism would work for a web app that's as customizable as Facebook, because each user request will require a slightly different response. I'd be interested in seeing Fujitsu chips enter the fray, I forgot to mention them in my post.

    5. Re:Well I suppose... by kzieli · · Score: 3, Informative
      There's actually 2 seperate points here
      1. the latest CPU's don't seem to be any better in practice then the previous model.
      2. Server OEM's are not delivering power efficient servers.

      the two points are somewhat independent of each other. The second I suspect is due to their being a lack of any standard for power efficent servers. Google did it by running single voltage power supplies. A standard around something like this would be useful, and not just for servers I suspect.

      --
      read my mind at http://the-willows.blogspot.com/
    6. Re:Well I suppose... by the+linux+geek · · Score: 1

      I was actually just throwing that in as an alternative. At my company, we use Itanic for machines in our compiler farm, running the Intel C Compiler. It gets excellent performance for this purpose; it does quite well on moderately parallel tasks and okay for floating point. I can't speak for how well it does for anything web-facing though. Out of the four I mentioned (POWER6, SPARC T1/T2, SPARC VIIIFX), its probably the worst-suited for this specific type of task. Of course, anything beats the shit that is x86.

    7. Re:Well I suppose... by Trixter · · Score: 3, Interesting

      I was just going to say that. If Facebook et al are not looking at the Sun coolthreads servers, they're idiots. A T5240 would deliver a whopping 128 hardware threads per 1u of rackspace.

    8. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      None of these offer much better performance. None. Please find me a general purpose (even niche) processor with higher performance than a high end Xeon across a variety of loads. Power? Nope. Anything from Sun? Nope. When Nehalem comes out it will not be possible to buy a general purpose CPU for anything up to 8 sockets (64 cores).

    9. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      I meant when Nehalem-EX comes out - Nehalem is of course out.

    10. Re:Well I suppose... by Anonymous Coward · · Score: 0

      Yes http://tech.slashdot.org/article.pl?sid=08/04/10/1152205 Power6

      http://www.tpc.org/tpcc/results/tpcc_perf_results.asp

      http://www-03.ibm.com/systems/power/hardware/benchmarks/

    11. Re:Well I suppose... by fishbowl · · Score: 2, Informative

      >None of these offer much better performance. None.

      There are IBM and Sun systems that are in an entirely different league, in terms of IO and memory bandwidth, than any Intel- or AMD-flavored system.

      --
      -fb Everything not expressly forbidden is now mandatory.
    12. Re:Well I suppose... by the+linux+geek · · Score: 0, Flamebait

      POWER6 absolutely ass-rapes Nehalem. Period. 4.7GHz (clocked up to 6GHz internally), faster per-cycle than any x86 processor currently on the market.

    13. Re:Well I suppose... by Anonymous Coward · · Score: 0

      All those Niagara hardware threads is good for throughput. Not performance. Sun sucks big time on performance. To bump up performance they had this whole Rock line of processors but they canned the whole thing.

    14. Re:Well I suppose... by lukas84 · · Score: 1

      I'm not sure what you're talking about, but our 10'000 CHF IBM x3650 M2 beat the shit out of the 50'000 CHF IBM Power 520.

    15. Re:Well I suppose... by lukas84 · · Score: 1

      IBM's POWER stuff is overpriced.

      You can get a two-quadcore machine from IBM for less than 10k (IBM x3650 M2).

      You can get a single-core-activated Power 520 for around 20-30k. The second 4.7 Ghz Power 6 Core is disabled. Also, this machine maxes out at 16GB of memory, while the x3650 M2 maxes out at 64GB (with the reasonably priced 4GB sticks - more with 8GB sticks).

    16. Re:Well I suppose... by the+linux+geek · · Score: 1

      I don't know what currency you're talking about, but the only single-core POWER 520 available is $5576US. Its still overpriced IMHO, but not nearly as much as you're saying. http://www-03.ibm.com/systems/power/hardware/520/browse_aix.html

    17. Re:Well I suppose... by Anonymous Coward · · Score: 0

      Let's see...
      IBM,
      Sun,
      Fujitsu,
      Itanium (yeah, its still Intel, but has great performance)...
      All of these can offer equivalent or much better performance at these kinds of applications than what they're using. Don't bitch if you're not willing to consider the alternatives.

      As far as I know, at least on IBM case, they aren`t alternative, they are actually market leader for enterprise CPUs. Why they got fixated on x86 is really beyond me. It is not like they will run Windows at Facebook servers.

    18. Re:Well I suppose... by Anonymous Coward · · Score: 0

      That is BS take a look to TPC results about Power6 http://www.tpc.org/tpcc/results/tpcc_perf_results.asp

    19. Re:Well I suppose... by tyrione · · Score: 1

      128 threads per CPU is meaningless if the code isn't designed to leverage those threads.

    20. Re:Well I suppose... by zefrer · · Score: 1

      Have you ever _used_ a coolthreads server? Sure it has lots of hardware threads but that's not going to do you any good if each of those threads runs so very very slowly.

      Having run benchmarks, a single Ultrasparc T2 (5120, 32 threads) performed on par with a single core of an Athlon Opteron 2000...

      It's not an accident that the Sparc architecture is dying off

    21. Re:Well I suppose... by drsmithy · · Score: 2, Informative

      POWER6 absolutely ass-rapes Nehalem. Period. 4.7GHz (clocked up to 6GHz internally), faster per-cycle than any x86 processor currently on the market.

      According to the SPECCPU2006 benchmarks, a 3.33Ghz Nehalem provides nearly identical performance to a 5Ghz POWER6 (@ 8 cores each).

    22. Re:Well I suppose... by lukas84 · · Score: 1

      The prices are in CHF and complete configurations - not sticker prices.

    23. Re:Well I suppose... by Anonymous Coward · · Score: 0

      POWER6 absolutely ass-rapes Nehalem. Period. 4.7GHz (clocked up to 6GHz internally), faster per-cycle than any x86 processor currently on the market.

      According to the SPECCPU2006 benchmarks, a 3.33Ghz Nehalem provides nearly identical performance to a 5Ghz POWER6 (@ 8 cores each).

      And I'm sure the Intel chip architecture scales just as well as the Power 6 architecture.

      NOT.

      Yeah, ass-rapes is accurate.

    24. Re:Well I suppose... by Anonymous Coward · · Score: 1, Informative

      I think you mean T5140. T5240 is the 2U version (which can have up to 256GB RAM and 16x 300GB SAS drives).

    25. Re:Well I suppose... by asaul · · Score: 3, Insightful

      Really? What sort of test was it?

      We took a Java application off a E6900 using 35% of 48 1.35Ghz US-IV cores. We put it on a T5240 with 16 1.4Ghz cores we saw it only use 14% of the machine with improved user response time.

      We also ran a database benchmark for some tests we were running between some AIX and Linux boxes and threw it against a T5240 running Oracle 11g for comparison. Because it was predominately a single threaded operation it ran slower than the 2.2Ghz Power5 LPAR, but the overall difference was about the same ratio as the difference in clock speeds. The thing to note was the machine was only a few percent utilised, so we could have run another 16 or so instances and coped easily.

      These machines are workhorses. Granted, you need the right workload but highly parallel/highly transactional work like java web applications or web serving absolutely fly.

      --
      "If everybody is thinking alike, somebody isn't thinking" - Gen. George S. Patton
    26. Re:Well I suppose... by Anonymous Coward · · Score: 0

      Well, I suppose that if he does not like the offerings from Intel and AMD, they could always go with...

      ARM - works well enough for the best selling video game console. It's all about cycles per watt.

    27. Re:Well I suppose... by WilliamBaughman · · Score: 1
      I never considered Itanium for a compile farm before, interesting. I can believe that it works well, I just have no idea how. Maybe that's because I don't know enough about compilers. Could it be related to the cache size?

      Of course, anything beats the shit that is x86.

      I wouldn't go as far as to say that. x86 may have inherited a lot of baggage, but there are a lot of really good x64 processors out there.

    28. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      Lol. Yeah. Compared to...? Nehalem EP? Nehalem EX? I don't think so. You're posting old benchmarks.

      http://www.itjungle.com/tfh/tfh041309-story01.html

      Nehalem chips currently out in dual processor mode murder in price performance (and are comparable or better in performance per processor). You guys really need to get with the times.

      Nehalem EX chips will extend this up to the 8-way domain.

    29. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      Unfortunately, for $5576 you could buy a Nehalem machine literally 10 times faster on many tasks, and 2-3 times faster on most.

    30. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      Indeed there are. Do you think Facebook is crunching numbers? Do you think Facebook is going to buy $100k machines?

      You can't buy faster commodity (think under $20k) hardware than the latest gen Xeons.

    31. Re:Well I suppose... by RightSaidFred99 · · Score: 1

      Right. You're full of shit and stuck in the 90's, dude. I tell you what, you buy the fastest dual processor machine you can for under $8000 that's not based on an x86 chip. I'll buy the fastest that is. We'll see who gets "ass-raped".

      Similarly, in a month or two let's extend that bet up to 8 cores. In fact, I'll buy a 4 core machine and you can buy an 8 core machine. We'll see who gets ass-raped.

      You "alternative architecture" guys crack me up. The battle is over - x86 has won at every level above the cell phone/PDA.

    32. Re:Well I suppose... by Anonymous Coward · · Score: 0

      According to the SPECCPU2006 benchmarks, a 3.33Ghz Nehalem provides nearly identical performance to a 5Ghz POWER6 (@ 8 cores each).

      And that's SPEC CPU2006 rate, i.e. the multicore/multithread version. The GP claimed it's faster per cycle than any x86... but if you look at the single thread version of SPEC, you'll find that Nehalem completely blows away POWER6. It's not even close.

  7. Well which is it? by Anonymous Coward · · Score: 0

    Do you want your servers to be cheap or do you want them to be good?

  8. ARM to the rescue? by bogaboga · · Score: 1

    "...To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient..."

    Sounds like ARM processors are being described here. Whether they can deliver is another subject in itself. On this front, I have my doubts on ARM's ability to deliver. That's my bias.

    1. Re:ARM to the rescue? by Anonymous Coward · · Score: 0

      What part of it do you doubt? That they're cheap? (They are) That they're super power efficient? (They are) That they can deliver? (ARM licenses out to dozens of other companies for actual production, so they're available in mass quantities)

    2. Re:ARM to the rescue? by digitalunity · · Score: 1

      As the AC noted, ARM's are available, cheap and power efficient. What they are not, however, is very powerful.

      They have their uses, but interpreting large amounts of crappy scripts is not one of ARM's strong points.

      --
      You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
    3. Re:ARM to the rescue? by sznupi · · Score: 1

      However, aren't ARMs so cheap (also in production, transistor-wise) and power efficient that you can throw 10 times as many at the problem (hey, seems you're operating a farm already) and still decisively win on price and power?

      --
      One that hath name thou can not otter
    4. Re:ARM to the rescue? by amorsen · · Score: 1

      You can't get massively-SMP (or NUMA) ARM machines. That means you're stuck with using lots and lots of machines, which again means you'll use too much space and spend too much money on switches etc.

      --
      Finally! A year of moderation! Ready for 2019?
    5. Re:ARM to the rescue? by sznupi · · Score: 1

      Well, yeah, somebody would have to build them; that was sorta the point (whether or not it's worth it).

      And actually...with ARM that's fairly straightforward in the sense that you're not on the whim of ARM (the company) - you just license their IP core and do whatever is sensible in your case. I might imagine Googles of the world doing just that at some point...

      --
      One that hath name thou can not otter
    6. Re:ARM to the rescue? by amorsen · · Score: 1

      They would need to make their own chipset to link the CPU's. Probably beyond Facebook's resources.

      You might have to implement better synchronisation primitives for the ARM architecture as well. It has taken x86 a long time to reach the point where 64-core servers actually deliver decent performance, and it will likely take a while for ARM too.

      --
      Finally! A year of moderation! Ready for 2019?
    7. Re:ARM to the rescue? by TheRaven64 · · Score: 1

      They are fast for anything that isn't too floating-point heavy (the recent ones have an FPU and one or two vector units, but they're not as heavily optimised as the integer stuff). Clock for clock, a Cortex A8 is close to an Atom in terms of performance (I was quite surprised by this) and the power envelope is an order of magnitude lower. If I were designing a server system for this kind of workload now, I'd put an 8x8 grid of something like TI's OMAP3 chips on the board. This gives you 64 cores, with 256MB of local RAM and 512MB of local flash storage (enough for the OS and the apps, keep the data on a SAN) in a total power envelope of 16W with the chips costing around $20 each (you don't need the DSP or GPU, so you can get the very cheap ones). At that power output, they can be passively cooled, but if you put some fans in the box then you can pack the boards closely together in a blade chassis.

      --
      I am TheRaven on Soylent News
    8. Re:ARM to the rescue? by mlts · · Score: 1

      There comes a point in diminishing returns with parallel tasking, where the time it takes to assign each CPU a task and gather the results after the number crunching.

      Some tasks like assigning a chunk of screen for ray tracing, the overhead to hand off to parallel tasks is low. You hand off the graphic commands, you get back a bitmap. However, there are other tasks that can't be split among CPUs as easily, such as I/O (which affects all the CPUs) or tasks that rely on another to finish (a disk encryption driver that is waiting for a drive buffer to fill up before it can decrypt the block and pass it to a waiting process for a read.)

      What might be a solution, though it would take some advanced architecture design on the Northbridge side of things would be to have multiple sets of cores. One set of cores would be faster (and thus fewer of them), and these would be weighted by the CPU scheduler for threads which can't be split as easily. Then, have a second set which would be slower, but there would be more of them. So an OS scheduler could hand tasks that can't be chunked up as much (such as encrypting/decrypting disks or packetizing/depacketizing network I/O) into a faster core, while things such as table calculations, graphics commands, and such could be handed off to the array of slower cores.

    9. Re:ARM to the rescue? by TheRaven64 · · Score: 1

      You can't get massively-SMP ARM machines, although the Cortex A9 and ARM11 both support up to 4-core chips. The power envelope is under 250mW per core (I don't have the exact figures, but the A8 and A9 use about the same amount of power and a 600MHz A8 board, including Flash, RAM, DSP and GPU cores, and a DVI framer uses 250mW). For this kind of workload, however, you don't really need SMP; you need lots of largely-independent machines. The power requirements and cost of current ARM chips are so low that you could build a cheap blade server with 64 chips (64 cores now, 256 in a year) each with its own local RAM and flash storage, and still come in under the power and financial budgets of an Intel system.

      --
      I am TheRaven on Soylent News
    10. Re:ARM to the rescue? by amorsen · · Score: 1

      Good luck with fitting your jobs in the tiny amount of memory and flash. If your chips are 1/10th as fast, you need to run 10 copies of your jobs for the same performance, and since you can't do SMP/NUMA, that means 10 times the memory.

      And then you need the 64-port ethernet switch to link it all.

      --
      Finally! A year of moderation! Ready for 2019?
    11. Re:ARM to the rescue? by sznupi · · Score: 1

      Of course, I wouldn't imagine that OS/software won't need changes for quite radical shift in overall system architecure (not like we don't do that already).

      BTW, specialized cores struck me as something that we're already planning to do with Larabee, Fusion and, generally, GPGPU (well...and Cell). Since we go that route already why not use the architecture that is unparalled in energy efficiency... (yeah, I know, x86 legacy)

      --
      One that hath name thou can not otter
    12. Re:ARM to the rescue? by mlts · · Score: 1

      That is definitely something to be pursued. Long term, one can see motherboards sporting special purpose cores, and an OS scheduler that can be made aware of them. For example, a special core for AES and its array shifting, FPU, GPU, and physics cores. The OS scheduler can weight tasks to run on a specialized CPU, so if the OS needs exponentiation for a RSA signature, the scheduler would find an idle core specialized in that first, if none are free, check if a general purpose core is free, and if that isn't the case, perhaps stick it on a GPU so it executes sub-optimally, but the job gets done.

      In the future, one can add more types of cores, perhaps a meta caching system to make a FPGA-like core which is tuned to what the computer does most often, be it I/O, crunching SSL in and out, database transforms, or graphical processing.

  9. Something about his arguement doesn't work by joeflies · · Score: 5, Insightful

    1) Facebook & Amazon need cheap, power efficient systems
    2) Intel and AMD aren't measuring up with processors to power these systems
    3) However, Google has systems appropriate for this use (presumably using Intel or AMD processors)

    If that's his argument, then it would seem that the real conclusion is that Facebook can't build systems as good as Google's, even though they are using the same processor technology.

    1. Re:Something about his arguement doesn't work by joeflies · · Score: 2, Insightful

      In addition, there seems to be something else wrong with his arguement

      "To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap"

      Which he later follows up with the following insight

      "There's a pretty simple answer for scaling infrastructure. It's, 'Don't be cheap,'"

      so which one is it?

    2. Re:Something about his arguement doesn't work by blackraven14250 · · Score: 2, Informative

      Server Cheapness != Data Center Cheapness

    3. Re:Something about his arguement doesn't work by Gazzonyx · · Score: 1

      I'd assume that the context of 'cheap' is different in both instances. On one hand, you want cheap per unit servers; OTOH, you want to buy many cheap units to be able to scale.
      Of course, that's just my interpretation...

      --

      If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.

    4. Re:Something about his arguement doesn't work by ushering05401 · · Score: 1

      so which one is it?

      Dunno, but I'm not gonna match wits with this guy when death is one the line.

    5. Re:Something about his arguement doesn't work by Hurricane78 · · Score: 1

      Both. Stupid people oversimplify. In this case, he did not mean cheap. He meant... damn, there is no English word for "preiswert". Essentially it is, when you get a good value for your money.
      He meant that you should buy much (don't be cheap) with little money (the servers have to be cheap).

      Of course, with that level of differentiation of thoughts, it's no wonder that he got problems. ^^

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:Something about his arguement doesn't work by Anonymous Coward · · Score: 0

      Word your looking for is thrifty.

    7. Re:Something about his arguement doesn't work by Anonymous Coward · · Score: 0

      damn, there is no English word for "preiswert".

      Oh, horseshit, you linguafop. Try "bang-for-buck", "price/performance", "figure-of-merit" or, at worst, "value".

      Don't ever accuse English of paucity of expression, unless you're talking about the Australian word for "the unique, subtle sweetness of deep-fried wallaby testicles in garlic sauce on a bed of artichoke hearts".

    8. Re:Something about his arguement doesn't work by TheLink · · Score: 1

      > unless you're talking about the Australian word for "the unique, subtle sweetness of deep-fried wallaby testicles in garlic sauce on a bed of artichoke hearts".

      What's the Australian word for that? I only know the related Australian phrase used in that scenario - "Needs more vegemite".

      The UK English word might be "Bollocks!", but I'm not English :).

      --
    9. Re:Something about his arguement doesn't work by Trepidity · · Score: 2, Insightful

      If that's his argument, then it would seem that the real conclusion is that Facebook can't build systems as good as Google's, even though they are using the same processor technology.

      Google does have approximately 30x as many employees as Facebook, so it's not implausible that they've got a much greater ability to build in-house custom tech.

    10. Re:Something about his arguement doesn't work by tyrione · · Score: 1

      If that's his argument, then it would seem that the real conclusion is that Facebook can't build systems as good as Google's, even though they are using the same processor technology.

      Google does have approximately 30x as many employees as Facebook, so it's not implausible that they've got a much greater ability to build in-house custom tech.

      NeXT Software came to Apple with 300 Employees, including HR and Accounting. Let's just say the quality of talent at NeXT was much greater than at Facebook.

    11. Re:Something about his arguement doesn't work by Anonymous Coward · · Score: 0

      or 'frugality', even...

    12. Re:Something about his arguement doesn't work by Nossie · · Score: 1

      "there is no English word for "preiswert""

      oh I dont know ... value ? :P

    13. Re:Something about his arguement doesn't work by Nossie · · Score: 1

      budget would actually fit really...

    14. Re:Something about his arguement doesn't work by ceoyoyo · · Score: 1

      It doesn't add up the other way either:

      1) Facebook needs cheap, power efficient systems.
      2) This guy is complaining because the chips aren't fast enough.

    15. Re:Something about his arguement doesn't work by happyhangone · · Score: 1

      Well, if they are bitching about AMD and Intel, he can call Dell's DCS and buy VIA systems or just buy the systems that Amazon, Google and others are purchasing (using Intel and AMD)

  10. PHP by Anonymous Coward · · Score: 3, Interesting

    And we're, literally in real time right now, trying to figure out why that is,' Heiliger said.

    It's because your shitty website doesn't have a single line of compiled code. PHP only goes so far.

    1. Re:PHP by afidel · · Score: 4, Interesting

      Yeah, this. Most of us don't have too much trouble wringing performance out of x64 processors when we need to. He wants a miracle of hardware he can throw at poor code which is NOT what Google asks for. Google simply want to wring every last flop/dollar (TCO) out of their systems which is slightly more than most of us need (the cost of engineering Google type solutions is more than 99.9+% of shops could reap through improved efficiency).

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:PHP by MightyMartian · · Score: 2, Insightful

      Exactly. All these interpreted languages, even with some special tricks, will have serious scalability issues. At some point you have to look at the application and ask some serious questions.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    3. Re:PHP by Anonymous Coward · · Score: 0

      You're a tool if you think they aren't using the Zend optimizer or APC keep the compiled byte-code cached. In the end, it's the same as running Java on a JVM.

    4. Re:PHP by digitalunity · · Score: 1

      Exactly. They should start small. Focus on performance profiling, find the most expensive parts of their code and reimplement those in a compiled language.

      If they're using Zend and still can't get the performance they need, they just need to accept that PHP's flexibility and rapid development friendliness come at a price-runtime speed.

      --
      You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
    5. Re:PHP by Anonymous Coward · · Score: 0

      People choose PHP because the gain in productivity is worth the loss in performance. Developers cost money too. A good developer's yearly salary and benefits, say $200K in total, costs as much as about 100 servers. Web companies decided using PHP was worth the reduced human costs and reduced time to market. Now whether AMD and Intel try to support the workload is their own problem, but if they don't, they shouldn't expect to sell too many Nehalems.

    6. Re:PHP by schon · · Score: 1

      If they're using Zend and still can't get the performance they need, they just need to accept that PHP's flexibility and rapid development friendliness come at a price-runtime speed.

      This has probably already happened at a lower level, but this is a manager - there must be someone to blame. I imagine a conversi

      VP: Why are our services so slow?

      Programmer: The software is running as fast as it can - it's not possible to make it faster without rewriting it in another language, or getting faster computers.

      VP: OK, how much to rewrite it?

      Programmer: Probably a couple of years, at $120,000 per programmer.

      VP: OK then, let's get faster hardware.

      Programmer: It doesn't exist.

      VP: Damn Intel and AMD - they can't solve our problem for us!

    7. Re:PHP by MightyMartian · · Score: 1

      In some ways it's a real pity that Perl became so ubiquitous in the early years of the web. I remember coding some early CGI forms in C, it just seemed logical, but everyone insisted "Perl is the language of the web", and it became pretty heavily frowned upon to run compiled code on a server. Then there was Python and PHP, but it's all the same at the end of the day. You can play some games to get interpreters cooking, but there are finite limits here, and to get beyond it, you're going to have to look at getting a lot closer to the metal.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    8. Re:PHP by hardwarefreak · · Score: 1

      Google simply want to wring every last flop/dollar (TCO) out of their systems...

      I think you meant MIP, not FLOP. Search engines don't require floating points calculations. It's all integer baby.

  11. Atom by sammykrupa · · Score: 0

    "the servers have to be cheap, and they have to be super power-efficient." So aren't Atom-based nettops using like 5 watts and dual core versions selling for $150, you supply the drive? http://www.newegg.com/Product/Product.aspx?Item=N82E16856167037

    1. Re:Atom by Anonymous Coward · · Score: 0

      Do you really think server farms need those desktop casings?

      http://www.logicsupply.com/products/boxd945gclf2

      BTW your link is "supply the drive and RAM". Mine is "supply the power supply, drive and RAM" but I think server farms would go for custom power supply anyway.

  12. Sun.... by Fallen+Kell · · Score: 2, Insightful

    Its the next logical solution... Those T5440 servers with 256 processing threads are MONSTERS in terms of handling simultaneous connections which make them very good web servers, database servers, and file servers, all of which means they are very good for a company who's product is a website.

    --
    We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
    1. Re:Sun.... by Anonymous Coward · · Score: 0

      Sun?.... you are crazy to go with sun and there platform now.. its all dead now..

    2. Re:Sun.... by Temkin · · Score: 2, Funny

      Sun?.... you are crazy to go with sun and there platform now.. its all dead now..

      Larry? Is that you?

    3. Re:Sun.... by Fallen+Kell · · Score: 2, Interesting

      Not really. What is dead is Rock. Coolthreads are here to stay, especially now that Oracle bought them. Niagra Falls is the fastest single server Oracle server currently in existence. Oracle is going to continue to build on that platform, with most speculation being that they are going to release a "black box" Oracle solution, which will simply be a drop in place, connect power and network, and turn the key solution, eliminating the need for the company that purchases said solution to have system admins who have had enough Oracle training to know how to properly setup a server to run the database. Oracle will then sell "support" for the systems on a tiered basis. It will most likely be based on the same platform as the Sun Unified Storage System line, like the 7410, even available with Oracle RAC as an option.

      --
      We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
    4. Re:Sun.... by zefrer · · Score: 1

      Uh not quite. Web servers sure, database? I think not. Having actually tried to do what you're suggesting, all those threads are no good if each of them sucks in terms of performance.

      Webservers/fileservers sure but it is too expensive to consider unless there aren't any other viable, cheaper options - which there are plenty of

    5. Re:Sun.... by thommym · · Score: 1

      Yupp, exactly the scenario I can see coming.

      --
      Don't feed the penguins
  13. I wonder if he's not thinking about scaling enough by filesiteguy · · Score: 1
    Honestly, I think that his arguments fall flat. Though I like FB as much as anybody, and I feel for someone dealing with massive performance needs - I only have a paltry 30 servers running my main application - I wonder if he's being realistic.

    There's a pretty simple answer for scaling infrastructure. It's, 'Don't be cheap,'" Heiliger said. He added that Facebook does drive hard bargains with its hardware and software infrastructure suppliers, and is careful not to overbuy.

    I remember reading about how Amazon does it. They have clusters of servers running whatever OS suits the particular person having written the portion of code being used and will blow through something like 100 dead servers a day. IIRC, when you load a page from Amazon you get content delivered by 20+ servers onto one web page.

    Maybe he just needs to scale out.

    Or - I just noticed an unused AS390 in the server room today. Apparently the Z890 that replaced it is also going to be replaced by a new z9 machine. He could bundle some apps on the z890 or the 390.

    I wonder if you can run .net or Java under OS/390 or MVS...

  14. Sounds like a bunch of excuses to me by stox · · Score: 4, Insightful

    Assuming that a solution was properly engineered, this should not have been a surprise.

    Cheap. power efficient, performance. Pick two.

    --
    "To those who are overly cautious, everything is impossible. "
    1. Re:Sounds like a bunch of excuses to me by Anonymous Coward · · Score: 0

      You don't have to pick two. It is perfectly possible to change the way you look at the problem and arrive at something which is cheaper, more power efficient and is faster.

      Google designed their own server systems. The fact they rolled their own resulted in it being cheaper. The fact they distributed the UPS meant it was more efficient, and they didn't sacrifice anything in CPU to get it.

      This "pick two" meme is BS, and has been since it came out. It's only "pick two" if you assume you can't change the rules.

    2. Re:Sounds like a bunch of excuses to me by rossifer · · Score: 2, Interesting

      Assuming that a solution was properly engineered, this should not have been a surprise.

      Cheap. power efficient, performance. Pick two.

      Actually, Google got all three of those in their system-level design (when cheap is measured per CPU). What they didn't get was per CPU reliability. That's pretty miserable by the standards of commercial servers. Luckily, all Google software is architected, designed, and written to work around frequent hardware failures, so that's ultimately covered.

    3. Re:Sounds like a bunch of excuses to me by cenc · · Score: 1

      I think this is something that most pure IT people fail to appreciate about Google's buisness model. They bought their freedom early. They designed their systems around being able to buy the cheapest crappiest whatever on the market, and have it keep on ticking no matter what. In the long run they saved way more money and leverage much more power in terms of market and CPU cycles, simply because they where not getting bent over the barrel by some vendor. That is exactly what facebook is complaining about. Google's bottom line is reflecting that freedom. They are not paying AMD, Intel, or any other company a large percentage of their take. Yea, they have suppliers, but they can tell them to go F themselves. They are Google after all.

      Facebook is unsustainable both in terms of infrastructure and buisness. In 2 or 3 years, no one will remember facebook; but I bet we will all still be using Google.

    4. Re:Sounds like a bunch of excuses to me by cheekyboy · · Score: 1

      I pick Utter Performance, then I pick Cheap Power + Cheap Computers.

      Who cares if it eats tonnes of cabon if its CHEAP, that equals profits.

      --
      Liberty freedom are no1, not dicks in suits.
  15. A Familiar Tune from Facebook by 1sockchuck · · Score: 3, Interesting

    This is becoming an annual event for Heiliger, who also complained about server vendors at GigaOm's Structure 08 conference last year. Facebook used to buy a lot of cloud-optimized gear from Rackable/SGI, but no longer appears on the list of their largest customers. Makes you wonder if they're not going to follow Google's lead and build their own servers.

    1. Re:A Familiar Tune from Facebook by briantf · · Score: 1

      Facebook is foolish; I just got a small setup in from Rackable for a client of mine. Spendy, but very well done, it will be cheap to keep over the next 3 years. Great pre-sales support, great install support, complete power and heat profile up front, and 50% more $$$ up front than a generic Dell rack system. Considering the track record of Dell for this same client over the last 8 years, the client will be $$$ ahead in less than 18 months. We just downsized the cooling system for the server room (!!!!) and the double redundant 48V power system is the bomb. I don't dig the SGI rebranding, but the Rackable folks know their stuff.

      It sounds as if Facebook feels entitled to loudly complain in order to get free/promo hardware. I guess Rackable wouldn't front them a couple of the ICE datacenter modules. Losing customers like Facebook sounds like a win.

      Regards,
      Brian in CA

    2. Re:A Familiar Tune from Facebook by cheekyboy · · Score: 1

      lets see , 1 motherboard + cpu & ram, and one disk (cheapest).

      Not bad, just 4 items to make a PC, the power can be worked out later.

      Design custom cases/racks, outsource the tool work, bingo, not hard at all, each PC could be under $150.

      --
      Liberty freedom are no1, not dicks in suits.
  16. Having a Bad Day? by FranTaylor · · Score: 1

    He woke up on the wrong side of the bed, and then he had to sign the check for the electric bill.

    He's just grumpy.

  17. Rub a lamp, Heiliger by SeaFox · · Score: 4, Insightful

    'You guys don't get it,' Heiliger said. 'To build servers for companies like Facebook, and Amazon, and other people who are operating fairly homogeneous applications, the servers have to be cheap, and they have to be super power-efficient.'

    NEWSFLASH! Customer are tightwads.

    Performance/Reliability/Price.

    Pick any two, Heiliger.

    1. Re:Rub a lamp, Heiliger by Phil06 · · Score: 1

      He could start charging Facebook users. Then he could afford better servers.

      --
      "...and yet, I blame society" Duke - Repo Man
    2. Re:Rub a lamp, Heiliger by theCoder · · Score: 1

      He could start charging Facebook users. Then he wouldn't need as many servers.

      :)

      --
      "Save the whales, feed the hungry, free the mallocs" -- author unknown
  18. Re:I wonder if he's not thinking about scaling eno by BBCWatcher · · Score: 1

    Facebook uses PHP, and yes you can, on both z/OS and Linux. Probably on z/TPF, too. And Facebook wouldn't be the first Internet company to buy a mainframe.

  19. The Technical VP of Facebook????? by Schnoogs · · Score: 1

    Let me file his opinion with my next door neighbor the plumber.

    1. Re:The Technical VP of Facebook????? by Anonymous Coward · · Score: 0

      You mean Joe the plumber?

      I hear he's really good at that politics thing.

  20. Re:I wonder if he's not thinking about scaling eno by dirtyhippie · · Score: 1

    Java? Yes, absolutely. Not sure about .net tho.

  21. Surely that's obvious by grahamsz · · Score: 3, Informative

    They collect a large amount of data on people and mine that for marketing information to turn around and target those same users.

    It's the same model as google.

    1. Re:Surely that's obvious by vux984 · · Score: 1

      Thanks. I'm not a facebook user. I didn't know to what extent they'd implemented targeted advertising.

    2. Re:Surely that's obvious by MaskedSlacker · · Score: 1

      HEAVILY. It's absurd. I get ads based on individual words from my profile.

    3. Re:Surely that's obvious by Darkness404 · · Score: 1

      Google has nothing on Facebook, put a band as one of your favorite artists and the next day you will see "buy tickets for X now" ads. Others will say "we need people *insert your age* years old for a study".

      --
      Taxation is legalized theft, no more, no less.
  22. so what about google then? by Klintus+Fang · · Score: 2, Insightful

    I'm bemused that he implies the problems with his servers are due to Intel and AMD no delivering with their chips, yet at the same time he admires google for how good a job they do in building out their machines.

    he must be aware that google uses Intel and AMD chips.

    his reasoning just doesn't square.

    --
    In a minute there is time For decisions and revisions which a minute will reverse. -T.S. Eliot
    1. Re:so what about google then? by hansamurai · · Score: 1

      He's complaining about two different things. The first is that AMD and Intel supposedly lie about their performance gains from one generation to the next. The second is that server vendors don't offer solutions to companies like Facebook that needs tons and tons of processing power for cheap and with low power consumption. In the first case he's more concerned about the lack of performance they're getting and in the second he's concerned about the lack of variety or customization the vendors are providing.

    2. Re:so what about google then? by Klintus+Fang · · Score: 1

      You are probably right. It'd be nice if he could say what precisely he thinks they are lying about. I mean, I know marketing is always exaggerated to some degree, but as rule, it seems to me that AMD and Intel processors do generally perform the way the companies claim they will if you look past the hype at the technical details.

      --
      In a minute there is time For decisions and revisions which a minute will reverse. -T.S. Eliot
    3. Re:so what about google then? by LackThereof · · Score: 1

      IIRC, Google doesn't use top-end "server" chips in their servers. They use consumer grade, midrange chips that they can get at cheap commodity prices, and load balance everything across a ton of machines.

      He implies the problems are due to Intel and AMD not delivering with their server chips; these are not the chips that Google is using.

      --
      Legalize recreational marijuana. Seriously.
    4. Re:so what about google then? by Klintus+Fang · · Score: 1

      agreed. which suggests the companies problem, if there really is one, is that they are not buying the machines that best fit the needs of their software stack.

      --
      In a minute there is time For decisions and revisions which a minute will reverse. -T.S. Eliot
  23. Re:I wonder if he's not thinking about scaling eno by Anonymous Coward · · Score: 0

    I wonder if you can run .net or Java under OS/390 or MVS...

    Yes, actually, though we've been calling it z/OS for about 10 years now, and it's an hybrid mix of MVS and Unix.
    Java definitely. Not sure if there's a .NET engine yet - might need to run Linux for z-Series in an LPAR or under z/VM to get a .NET framework

  24. And yet... by Junta · · Score: 5, Interesting

    Every major server vendor has jumped on the bandwagon of 'look how efficient we are, and 'cheap'. Three years ago, by and large the tier ones wouldn't bother designing systems without forcing even the cheap design to have parts included to facilitate purchase of redundant add-ons (i.e. power distribution cards designed for dual power supplies regardless of one being bought or not). They would always put a high end storage controller on the planar. They would always make their 'entry' platform be burdened with expensive components to make it easier to option it up.

    Now, we have tons of 'internet scale', or 'cloud', or whatever buzzword you feel like. They tend to stress energy efficiency, low cost components, with sales and management strategies targeted at thousands of servers (i.e. IBM iDataplex, HP SL6000). Basically, precisely what he prescribes, though probably not as 'cheap' as he wants. The incentive he gives is that the vendors should have zero margin, which is not particularly compelling for companies to work toward. Google's situation works because they brought it in-house and thus have fewer middle-men. Honestly, from all the rumours I hear, it's the logical thing to do when your server consumption is larger than some respectable computer companies' entire production. If he thinks the volume of servers is high enough to pull a google, by all means do it. Otherwise, be prepared for people not jump at the chance to give their designs to him at zero margin.

    Of course, if he is calling them out on performance per-watt by avoiding non-x86 solutions, including ARM, that might be a fair criticism. However, I think company forays into 'exotic' architectures have not panned out in the market recently. Sun's niagra, despite all the worthy praise, couldn't attract a mass-market required to subsidize it for those who benefited most from it. Last year, IBM seemed to be saying Cell architecture would light the world on fire, but have been a lot quieter about it now. The message their buisness leaders have probably taken in is that while these things have their target market, that market isn't worth the expense of developing products that are refused by the larger market and focus instead on leveraging commonly accepted building blocks to do as best they can for that niche, even if it means skipping the 'perfect' solution. Sure, IBM still sells plenty of POWER, but I haven't heard that be *particularly* praised on the performance/watt category like I hear a lot for Niagra, Cell, and ARM. And if not for POWER's legacy, it probably would be still born in the market today. The PA-RISC->Itanium decision for HP probably sank their HP-UX product line faster than banking on legacy of PA-RISC installs, and it seems IBM won't make that mistake, but at the same time I don't hear much about *new* POWER customers.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  25. Depends on 'headroom' of other subsystems. by Kadin2048 · · Score: 2, Informative

    Not necessarily, no.

    It's all about how CPU limited the workload is.

    You might be running a program that's CPU limited on one processor, then upgrade the processor and discover that it's suddenly discover that instead of being CPU-bound, now you're memory-bound. Or I/O bound. Or whatever.

    Point is, just because you've hit the wall in terms of CPU doesn't mean you'll get a 50% improvement with a 50% increase in CPU ... you'll only get that if all the rest of the server's systems have 50% overhead to spare. And in most cases they don't. One of them will hit the performance wall before you return to being CPU-bound with the shiny new processor.

    There are exceptions to this -- renderfarms, for instance, or some distributed HPC stuff -- where you really can reasonably expect to get 50% more performance out of 50% more CPU, but they're exceptions not the rule.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:Depends on 'headroom' of other subsystems. by evanbd · · Score: 1

      Well, more generally, you have to apply Amdahl's law. Most complicated programs operate in a realm where there aren't well defined bottlenecks, and you can get more performance through more computer power, more memory, faster memory, faster disks, faster networking...

      The point I was trying to make is that if you have crap code, and throw more compute power at it, it's unreasonable to expect it to perform like it isn't crap code -- but probably entirely reasonable to expect faster crap code.

    2. Re:Depends on 'headroom' of other subsystems. by Jah-Wren+Ryel · · Score: 1

      Unless the crap is something stupid like holding a spinlock while waiting for a web-browser to finish transfering a file. Then what appears to be cpu bound (because of all the spinning) is actually limited by the speed of the clients and to a lesser extent, the size of the pipe to the clients.

      --
      When information is power, privacy is freedom.
    3. Re:Depends on 'headroom' of other subsystems. by lauwersw · · Score: 1

      Or just the classical scaling issues when adding more cores and more threads, such that the threads are waiting for each other on locks. It's usually worse because multi core processors are typically clocked slower. So you have more threads but they execute slower each, causing the lock to be held longer by each thread, causing more lock contention...

  26. Strange... by spire3661 · · Score: 4, Informative

    Since when do we listen to manufacturer's claims? You take the new hardware, stress test it with your custom software, record results, plan servers accordingly. How hard is it really to commission a server design that meets your needs and then QA some prototypes?

    --
    Good-bye
    1. Re:Strange... by edmudama · · Score: 1

      Mod the above up.

      Intel, AMD, Sun, HP, Dell, IBM, whoever. They all provide a wide range of configurable, scalable, inexpensive (to expensive) building blocks to get your business need accomplished. With all the amazing things that have been created using computers in the last thirty or forty years, I can't blame the providers of those building blocks for something not coming together. The latest chips are absolutely faster than previous ones, but maybe you need to rethink your network fabric? Maybe your storage subsystem? Maybe your application design? Who knows where their problem really lies.

      If anyone could throw together a few white boxes for next to nothing and build something to survive facebook's traffic volumes, then there wouldn't be any jobs for smart IT folks, would there? Google seems to have figured something out, Amazon seems to have figured something out, maybe Facebook needs to apply more brains to their problem instead of complaining.

      --
      More data, damnit!
    2. Re:Strange... by Arimus · · Score: 1

      With facebook I'd guess the bottleneck ain't at the hardware level... php while good for alot of website work I'm not convinced is the best solution for the volume of traffic and size of pages that facebook delivers.

      Once they sort their software architecture out they can then look at the hardware; starting with the disk storage systems and network fabric, the cpu is the least of their worries until they solve all the other bottlenecks in the line before the CPU gets invovled. No matter how fast a CPU is it can only operate as fast as it can get data and instructions shoveled into it.

      --
      --- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
    3. Re:Strange... by Anonymous Coward · · Score: 0

      This is Facebook we're talking about. Their code is a mess of PHP on top of MySQL that simply doesn't scale. The presentation on their infrastructure a few months ago was almost funny. IIRC, they have 5000 servers to handle 30,000 requests per second. And they've even had to jump through hoops to get that to work. For instance, they don't do database joins because they can't get replication to work in a timely fashion, so different data resides on different database clusters. I would be surprised if they were able to simulate their actual production environment on a smaller scale. They probably did do testing, but not with their actual application code, so machines that may have passed their stress testing could be under-performing once they reach the production environment.

      So they're left in a situation where they have no revenue to speak of and run heavily in the red and can only scale by buying more and more hardware. They've got a decent size chunk of cash in the bank, but operational costs are eating through it quite quickly. So rather than (or possibly in addition to) re-architecting their application to scale better, they're publicly chastising server makers for not advancing at a rate that will bail them out of their current mess.

      What Facebook needs to do is re-write their application in a technology that scales and run it on technology that scales. It would be a difficult process, but in the long run, it's what they need to survive. The logical choice would be, IMHO Java. I may be biased since I work on a Java-based application, but I know it can scale since we've reached 5000 requests per second on 5 app servers and 2 database servers while maintaining sub-second page generation times on all but the most involved pages. The load at the time was about 50% on the database servers and around 30% on the app servers. FWIW, our application is considerably more complex that Facebook's is, though less bandwidth intensive.

  27. ARM? by sznupi · · Score: 1

    I wonder when we'll see servers with CPUs based on (many...) ARM cores.

    Yes, they are an order of magnitude slower, but three orders of magnitude more power efficient. For the same CPU performance you'd probably be around two orders of magnitude more power efficient (for CPUs at least). If your app runs on a large farm already...

    --
    One that hath name thou can not otter
  28. Would you expect otherwise by Chuck+Chunder · · Score: 4, Funny

    If that's his argument, then it would seem that the real conclusion is that Facebook can't build systems as good as Google's

    Google's core business is intelligence.
    Facebooks core business is stupidity.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:Would you expect otherwise by Tablizer · · Score: 1

      Google's core business is intelligence.
      Facebook's core business is stupidity.

      What's the equation for stupidity?
         

    2. Re:Would you expect otherwise by vic-traill · · Score: 1

      Google's core business is intelligence. Facebooks core business is stupidity.

      .

      That's a god-damned beaut, brother. I actually spewed some yogurt into my nose, I started laughing so hard in mid-swallow.

      If I had my way around here - which of course I don't - you'd get some bonus/recognition cool award thing. Not mod points, but like an instant order of magnitude reduction in your /. UID.

      Not that you really need it, now that I've looked at your UID, but hey, it's the thought that counts, right?

      --
      [17] Leary, T., White, C., Wood, P. R., Bhabha, W. D., and Wirth, N. Lambda calculus considered harmful. In Proceedings
  29. Improve the effieciency of the back-end! by achacha · · Score: 1

    I bet if they rewrote the CPU intensive parts in C/C++ (from PHP) they could reduce the overall machine count and stop worrying about which CPU manufacturer lied to them that week :)

  30. Jonathan Heiliger can kiss my rosy ass... by hyades1 · · Score: 0, Troll

    Ever since I accepted their invitation to use my (very unusual) name openly on Facebook, every single variation on that name has been spammed. This Heilinger jackass can take his "harsh words" about the performance of people who do real hardware work and shove them deep and hard. You can't bullshit a chip, you can merely mis-state its performance. When you lie about how you'll protect information people give you in trust, you're pretty much a douchebag. Mr. Heiliger, you are a douchebag.

    --
    I've calculated my velocity with such exquisite precision that I have no idea where I am.
    1. Re:Jonathan Heiliger can kiss my rosy ass... by hyades1 · · Score: 1

      Whatever idiot labeled this a "Troll" is probably incompetent to be given moderator status. Try studying the legal interpretation of "Fair Comment", jackass.

      --
      I've calculated my velocity with such exquisite precision that I have no idea where I am.
  31. Hang on a minute... by OneSmartFellow · · Score: 3, Funny

    ...I'm supposed to care about the comments of the guy who wrote Facebook ?

    Hah, hah, hah, hah, hah !At least google needed to actually engineer their solution, but Facebook, come on ! The next time I need to write a PHP script for displaying photos and text, I'll hire my 13 year old daughter.

  32. and.. by Anonymous Coward · · Score: 0

    the servers have to be cheap, and they have to be super power-efficient.

    yeah, and self-replicating too!

  33. Wrong tool for the job? by Ihlosi · · Score: 1

    I don't think that Amazon, Facebook, etc, need all the floating point performance that current desktop and server CPUs can deliver. If they're really looking for power efficiency, they shouldn't use CPUs with features that are never used, but draw tons of power nonetheless.

  34. not just the CPU it's overall system performance by unix_geek_512 · · Score: 3, Insightful

    This isn't just about the CPU, it's about overall system performance.

    Despite improvements in CPU performance, memory and IO performance is lagging behind.

    A modern SATA drive delivers about 90MB/sec ( peak sequential read ).

    Some RAID controllers can do about 600-800MB/sec ( peak sequential read ).

    An average AM2 ( K10 core 65nm ) gets about 34,849MB/sec L1, 12,169MB/sec L2, 6371MB/sec L3, 2,741MB/sec DDR2-800 5-5-5-12.

    Obviously Opterons scale a lot better since they each have an onboard memory controller and additional HT links which greatly increases bandwidth as you add more CPUs. However adding more cores on the same die which have to share a single memory controller can cause starvation.

    Another major issue is software parallelization, writing parallel code is still a difficult problem. If your software doesn't parallelize well it doesn't matter if you have 8, 16 or even 32cores on a single die.

    If you had an equal number of CPU cores and memory controllers you could achieve much better performance, however your relatively very slow storage subsystems would still be a major bottleneck.

  35. 99.99% by Colin+Smith · · Score: 1

    Of server manufacturers customers are not Google, or Amazon or Facebook. The VP doesn't get that he's just not that important....
       

    --
    Deleted
  36. and this is why... by RMH101 · · Score: 1

    ...big companies have infrastructure architects to plan, test and make recommendations on new infrastructure. You don't just go out and buy a container load of the latest and greatest based on the advertising copy.

  37. PHP "extension" by RGRistroph · · Score: 4, Insightful

    I once did a large project in which I took a large, slow site in PHP (it was pretty complecated, it was a CRM with a lot of custom business logic) and rewrote all the core functionality from PHP to C / C++, and made it a "module" of PHP. The rewriting was mostly simple translation -- litterally removing all dollar signs, adding some types, and attempting to compile, and just fixing the compile errors until it would build. Then going back through it with a fine-tooth comb to track down all the memory leaks.

    The speed increase from doing that is pretty surprising. Simple loops that do a bit of math or something speed up by 100 times, and a loop that creates and destroys an object within the loop will be 100,000 times faster. This is without actually trying to write fast C/C++ code, and not create and delete the same thing over and over in a loop -- just pure dumb translation of the code.

    At that point, the web site guys can keep tweaking and changing the web page in PHP just like before; but they load that module in the php.ini and then they have a basic library of stuff, like login_user() or get_user_balance() and etc, that are really fast and do all the heavy lifting.

    I would be surprised if Facebook has not already done this. How to do it is well documented in several books, and there are lots of PHP modules written in C/C++ to look at for examples.

    I suspect that Facebook's VP is right that AMD and Intel exaggerate their claims, but is also generally true that most computer programs are more IO bound that you expect. This is not a reason to avoid something like I describe above; once you have the more complete control of programming in C, IO issues may be easier to find and address.

    He also mentions that the servers offered by Dell and others aren't very power efficient or practicle for him, and he mentions Google designing their own servers. Nothing google did was really rocket science, from what we know, and Facebook probably doesn't have to go as far as they did to get a reasonable benefit. It's not that hard to set up motherboards to run without a case, booting off the network with no harddrive attached.

    1. Re:PHP "extension" by TheRaven64 · · Score: 1

      The speed increase from doing that is pretty surprising. Simple loops that do a bit of math or something speed up by 100 times, and a loop that creates and destroys an object within the loop will be 100,000 times faster. This is without actually trying to write fast C/C++ code, and not create and delete the same thing over and over in a loop -- just pure dumb translation of the code.

      How can the PHP developers produce something that sucks so much? I haven't spent much time on optimisation yet for my Smalltalk compiler, but for computing the fibonacci sequence naively it only takes 60% longer than the same algorithm in Objective-C. Being 100 times slower takes real skill; even my first, really horrible, implementation was only 30x slower. Once I started doing the overflow checks in hardware (C / Objective-C doesn't do them at all, but for Smalltalk I need to transparently box integers if they overflow) instead of software the speed jumped to the current speed. And this is without any clever type inference or method specialisation (which any half-decent Smalltalk or Self implementation has been doing for the last 20 years) because this is something that I've been working on by myself in my spare time for less than a year. A team with the resources of the PHP developers should be able to do much better.

      --
      I am TheRaven on Soylent News
  38. overblown company claims by Anonymous Coward · · Score: 0

    I bet intel/amds performance claims are closer to reality than facebooks book value.

  39. Re:I wonder if he's not thinking about scaling eno by amorsen · · Score: 1

    Mainframes aren't known for good CPU performance. Brilliant at I/O, but if Facebook is I/O-limited they're either doing something very wrong or something very right.

    --
    Finally! A year of moderation! Ready for 2019?
  40. Slashvertisement? Excellent article at CNET. by Futurepower(R) · · Score: 1

    Excellent article at CNET.

    The Slashdot article seems to be a way of getting people to see ITworld; is it a paid ad? It was not clear from the ITworld article what problems the Facebook V.P. had with AMD and Intel. If what he wanted to say could be understood better, I doubt it would be controversial.

  41. Hey! Leave lying about harware by Anonymous Coward · · Score: 0

    to Apple. That is the only thing that they are good at.

  42. What's your experience? by jernejk · · Score: 1

    I'm just about to buy a new server and I'd like to hear from slashdot what's your experience with the new CPUs? Should I buy the new 55 or the old 54 series?

  43. Performance issues, eh. by jjgm · · Score: 1

    PALO ALTO (Reuters). PHP-based website reports scalability problems. Blames server hardware. Film at 11.

  44. Facebook should buy SiCortex by White+Flame · · Score: 1

    They're on the block, and produce incredibly power-efficient, inexpensive (complete systems for ~$200/core to the end user) machines. Their sales were continually gaining momentum, but their investors hit troubled times and had to pull out.

  45. seriously guys... by nimbius · · Score: 1

    how many mips does it take to run a database full of one-liner updates about someones cat, or boyfriends girlfriends ex fiance?

    unless bejewelled is actually running as a computational cluster app, you folks have far LESS to bitch about than a web-business or the worlds largest search engine in my opinion. find a more efficient operating system, and insist more efficient code. you dont bitch at vendors for performance, you find other ones if it gets bad enough. im sure Cray would love to hear from you guys, or perhaps maybe SGI?

    --
    Good people go to bed earlier.
  46. Super power efficiency? by Tragedy4u · · Score: 1

    What grown man, let alone a VP of technology would use the word SUPER to describe something technical?

  47. Better Software helps by happy_place · · Score: 1

    No matter how much faster hardware gets, the software has to take advantage of the improvements. If you're using a bloated interpreted web-based language running on an OS that's not fine-tuned to your given piece of hardware and don't see huge improvements, perhaps one should evaluate the layers of innefficient code that you've rested your apps on... The Gaming Industry has had a lot of success in eeking out every cycle of performance possible, but they spend time tuning their products to hardware solutions.

    --
    http://www.beanleafpress.com
  48. You nearly owed me a keyboard there :) by Benanov · · Score: 1

    Your humor almost cost me my Kinesis keyboard (and they're not cheap)!

    That was absolutely brilliant.

  49. I wonder.. by Hoonis · · Score: 1

    Are they using the intel compiler?
    Are they making their binaries more thread-friendly?
    Are they using cc flags that exploit the new cache/features/instructions?
    Are they running their OS's with at least basic tuning to contain interrupts and kernel activity to particular CPUs?
    Are they using new hyperthreading efficiently and consciously or just disabling it?
    Are they running with taskset wrappers to decrease context switching on an obviously stochastic workload?
    Are they tweaking their networking configuration internally to optimize for their specific packet loads?

    Because I've found that the new hardware (Nehalems, for example) will give you a heck of a speed boost if you're doing the above.

    It's real easy to have the compatibility features mask performance, really you gotta look at it like a new platform.

    Anyway, those comments smell like making excuses to me, they are not even remotely specific enough to be defensible.

  50. -48V DC by Anonymous Coward · · Score: 0

    Telcos have been using -48V DC for their equipment for decades. Don't see why the non-telco crowd can't do the same and increase efficient by removing power AC/DC power conversion.

  51. random I/O vs. sequential I/O by Anonymous Coward · · Score: 0

    It's not even a full order of magnitude faster, but 112MB/s is still nearly four times faster. And these are both magnetic discs, rather than SSDs.

    Only if you're doing purely sequential writes. This only happens if you're laying down 20+ MB files at a time, or you're using a file system that is COW (like Btrfs, ZFS, BSD's LFS).

    If you're using ext3, with small- to medium- sized files, then you're getting head seeks and probably not getting 112 MB/s.

  52. Yeah ok! by kuei12 · · Score: 1

    I'm thinkin this fella Jonathan Heiliger is probably disappointed because he is probably running Dell Power Edge servers he bought off someone on Craigslist. That would explain the lack of chip performance. Does he have any clue that google is probably running intel/amd chips? They may have designed their own servers, but not the chips.

  53. Re:not just the CPU it's overall system performanc by the_denman · · Score: 1

    see Amdahl's law for more about speedup gain for any one part of a problem.

  54. When does it make sense...? by Targon · · Score: 1

    AMD and Intel are in the position where they need to make products used by a large number of customers. As a result of this, their primary focus will be on making products that will draw in the greatest number of customers. As we saw with Itanium, if the customer base is not large enough, the R&D costs will never be made up.

    So, when does it make sense for a chip and motherboard supplier to make a product with only one or two POTENTIAL customers in mind? Never is the answer that comes to mind. Both AMD and Intel MUST spend their resources on making products that will result in a net profit.

    So, Facebook and web servers, and database engines...it should be possible for AMD or Intel to make a platform with these specific applications in mind, but the cost for such a specific product to be developed when there are very few potential customers that would want it would be small. Potential is the key, because I am sure that if Facebook approached AMD or Intel and wanted a fixed-purpose product to be developed, they would be happy to do it for the right price.

    When a company makes a motherboard, the focus is to make a product that will get enough interest and sales to make a profit. As a result, we see motherboards with extra PCI, PCI Express, memory, USB, SATA, and other connectors than most people would actually need. If it gets cut back to only what would be needed for a specific customer, then the machine would probably perform better. Expecting a product aimed at a large number of people to be perfectly optimized and customized for any one specific purpose is foolish.

    And of course, you have the limitations inherent in any system, including bandwidth between components, ethernet controllers, and how much CPU power may be used for things like USB, SATA, and ethernet. When you buy a $75 motherboard and expect the performance of a $250 motherboard, you are pretty much guaranteed to be disappointed.

  55. Coolthreads by Anonymous Coward · · Score: 0

    If they want performance per watt, why don't they use sun ultrasparc t1 or t2? Massive throughput specifically optimized for web applications.

  56. Spoiled Rotten Little Kid by Anonymous Coward · · Score: 0

    Start Looking For A New Job Jonathan ?

    I think Jonathan Heiliger, VP of technical operations should first try keeping Facebook from crashing constantly. I can't go 5 minutes without the site locking up on me. Mr. Heiliger, really not impressed ! These chip makers are the one's that are keeping America Safe, right now and into the future. If you want to bad mouth someone Jonathan, bad mouth the people that work under you, that can't even keep Facebook a site worth going to anymore. You are a Spoiled Rotten Little Kid that thinks someone owes you something, the chip makers don't. Keep working harder on Facebook !

  57. Why the F--- do I need to subsidize Facebook? by tjstork · · Score: 1

    What the VP of Facebook is really asking is that Intel and AMD spend a lot of their R&D on designing features they want, and then pass those costs onto consumers everywhere, so Facebook can get cheaper servers.

    F--- that.

    --
    This is my sig.
  58. facebook vp must know they are designed for vm's by Anonymous Coward · · Score: 0

    LOL the new ones were designed for VM's really... haha thats why they do all the hardware virtulization and Virtulized i/o and they pimp it showing it. They could take advantage of super computers and drain there drops out of them if they built on the vm cloud. but it's just easier to do googles approach and much cheaper. But for paying customers they will want to buy the warranty and support because they are selling a service. Facebook guy needs a life.