4 ms·
We are actually working on a storage service called RESTBase (https://www.mediawiki.org/wiki/RESTBase https://www.mediawiki.org/wiki/RESTBase). RESTBase has plu
by gwicke 12y ago
We are actually working on a storage service called RESTBase (https://www.mediawiki.org/wiki/RESTBase https://www.mediawiki.org/wiki/RESTBase). RESTBase has pluggable table storage backends, starting with Cassandra. Other backends will scale this down for small installations.
The medium-term goal is to store all revisions as HTML, so that views and HTML-based saves can become storage-bound operations with low double-digit ms latencies. This will mostly eliminate the remaining 2-4% of cache misses, and should get us closer to actual DC fail-over without completely cold caches.
There is still a large amount of work to be done until all the puzzle pieces for this are in place, but we are hard at work to make it a reality. A major one, the bidirectional conversion between wikitext and HTML in Parsoid (https://www.mediawiki.org/wiki/Parsoid https://www.mediawiki.org/wiki/Parsoid), is already powering VisualEditor and a bunch of other projects (https://www.mediawiki.org/wiki/Parsoid/Users https://www.mediawiki.org/wiki/Parsoid/Users). Watch this space ;)
- tracker1 12y agoThanks for letting me know... I had some exposure to C* while at GoDaddy, and it would seem to be a great fit for what you are talking about... GD is using it to store user-generated content, and it works very well, most responses (lookup and processing) were sub 20ms consistently under heavy load... (I'm hoping they write a DNS service that does similar).