Yeah we've been running 0.10 in development for Parsoid for a while. So no
problems expected... other than unpredictable load gremlins or some such.
It sounds like gwicke's plan is to ramp up the load gradually to try to
head that off.
--scott
On Nov 13, 2013 6:02 PM, "Matthew Walker" <mwalker(a)wikimedia.org> wrote:
Hey,
For the new renderer backend for the Collections Extension we've come up
with a tentative architecture that we would like operations buy in on. The
living document is here [1]. It's worth saying explicitly that whatever
setup we use must be able to handle the greater than 150k requests a day we
serve using the old setup.
Basically we're looking at having
* 'render servers' run node.js
* doing job management in Redis
* rendering content using PhantomJS and/or Latex
* storing rendered files locally on the render servers (and streaming the
rendered results through MediaWiki -- this is how it's done now as well).
* having a garbage collector run routinely on the render servers to
cleanup old stale content
Post comments to the talk page please :)
[1 ]https://www.mediawiki.org/wiki/PDF_rendering/Architecture
~Matt Walker
Wikimedia Foundation
Fundraising Technology Team