The chromium-render service ("Proton") will eventually be replacing the electron-render / pdfrender service in production. This task encompasses the work to identify on what server it will live on. Performance estimates are captured in T178278. Additionally, the service requires a Debian Stretch installation.
- Mentioned In
- T178665: [Spike, 8hrs] Grave kerning issues and spacing issues in PDFs generated by Chromium (and previous Electron) via "Download as PDF"
- Mentioned Here
- T178189: [spike] Temporarily allow pushing large objects
T186748: [EPIC] New service request: chromium-render/deploy
T178278: Performance test the service
- Install Proton to a virtual machine.
- Find a spare machine and install Proton.
- Some other to-be-determined option from Ops.
The major blocker is that the Proton service requires a Debian Stretch operating system and current thinking is that, despite low traffic, it's too complicated and not a good candidate for a "first service" on Kubernetes. @mobrovac will update this ticket or ping us when he meets with Ops. Looking further ahead once this service is deployed, we’ll replay Electron renderer traffic to verify the load can be handled by Proton.
Hey @mobrovac. We're making final plans for the current quarter. Any idea when we should expect a place for the Proton production server to be available? I'm happy to continue the patches we worked on with @Pchelolo or clarify any ambiguities. Let me know how I can help you help us! Thank you! /cc @ovasileva @thcipriani
- decide where to put it in production
- get the service working in beta
- work towards getting it in production
- enable traffic from RESTBase to it for the test phase