ribena flavoured crisps
Most stuff is going to be served out of mem anyway, so disk speed is irrelevant, and it's hardly a trick to lay stuff down sequentially on disk. Starting with an empty disk and managing allocations yourself would do that no probs.
> "applications access files with consistent pathnames, avoiding risky namespace updates as capacity increases." Could this be an object-like storage approach?
dunno, it sounds like a fixed key denoting given featureless blob of data. A bit like a relational database in style. Nothing to do with objects
> We're told that clients access files with consistent pathnames but files can move in the cluster and we don't know how the client's pathname is associated with an actual file location.
Perhaps a distributed hash jobbie like memcached to manage the keys.
> AdMob, is cited by MaxiScale to support the product. It's described as the world's largest mobile advertising marketplace, with over 110 billion ad impressions served in 3 years
110 billion ads in ~90 million seconds = 1,200 per second. A worthless figure indicating no particular load without further info on spikes, growth, use of intermediate caches (or their abuse by cachebusting) ect ect.
Sounds like marketing.
Biting the hand that feeds IT
