Introducing paid subscriptions on GitLab.com

Re:Introducing paid subscriptions on GitLab.com by ishitatsuyuki on Wednesday April 12, 2017 @03:45AM (#14095622)

I doubt their infrastructure would scale well, even with more income. They still haven't adopt WebSocket/Rails 5, and this would attract more CI runners to DDoS their database.

[ Parent | on HN ]

Re:Introducing paid subscriptions on GitLab.com by narrowtux on Wednesday April 12, 2017 @05:56AM (#14096187)

This sounds like you threw in a few buzzwords. Why would a CI runner DDoS their database? How would WebSockets help them scale?

[ Parent | on HN ]

Re:Introducing paid subscriptions on GitLab.com by ishitatsuyuki on Wednesday April 12, 2017 @06:39AM (#14096381)

They doesn't use any long polling method but periodical fetching method for getting pending CI jobs. This causes massive lock on their database, and once it bring down the server entirely.

[ Parent | on HN ]

Re:Introducing paid subscriptions on GitLab.com by cmatija on Wednesday April 12, 2017 @07:56AM (#14096756)

Heya,

Just wanted to let you know that we introduced long pooling with GitLab Runner version 1.9.0 (~ three months ago).

Also you might want to take a gander at https://about.gitlab.com/2017/04/10/upcoming-runner-changes-... We're throttling older runners.

[ Parent | on HN ]

Re:Introducing paid subscriptions on GitLab.com by narrowtux on Wednesday April 12, 2017 @07:10AM (#14096540)

Per worker? That seems bad, yes.

[ Parent | on HN ]