"It's not like we have anything special (or x86-specific, Jasper!) other than very high bandwidth."
Wikimedia Labs uses x86 hardware virtualization (just one example). We already have transit linkages that include fiber, and new fiber is far from cheap. You persist in ignoring the costs of buying equipment. In terms of orders of magnitude, ~500 servers * $200 per server = $100,000 already. That is a conservative $200/server estimate that also doesn't take into account labor and other costs. To the level we'd want it, it's at least one more order of magnitude more expensive (no, we're not going to recover the costs by selling our existing servers). On Sun, Dec 29, 2013 at 10:10 PM, James Salsman <jsals...@gmail.com> wrote: > > Maximum 100 Mbps ethernet connection.... > > We should be using fiber, which also costs less power and is orders of > magnitude faster. > > If the words "enterprise-class" actually mean something more than > "much larger markup than purchasing components" then go with something > like http://www.marvell.com/company/news/pressDetail.do?releaseID=3576 > > For example, maybe the http://www.mitac.com/business/gfx_servers.html > people have benchmarks representative of our DB/cache usage patterns. > It's not like we have anything special (or x86-specific, Jasper!) > other than very high bandwidth. > > At least put out an RFP, please. > > _______________________________________________ > Wikimedia-l mailing list > Wikimediaemail@example.com > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ Wikimedia-l mailing list Wikimediafirstname.lastname@example.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>