sytse

86 ms·

1. 841.▲
   by sytse 8y ago

   Thanks, glad to hear you like the job we're doing.
2. 842.▲
   by sytse 8y ago

   Thanks, I've included it with https://gitlab.com/gitlab-com/www-gitlab-com/commit/8e9000b0...
3. 843.▲
   by sytse 8y ago

   Makes sense. With Heroku I used to run a monitoring service that made a request every minute to prevent this.
4. 844.▲
   by sytse 8y ago

   Thanks for commenting Dan! Interesting that AWS Lambda is also running containers instead of reusing processes. Their pricing suggests that Lambda is more efficient then containers, but maybe they priced it while anticipating being able to
5. 845.▲
   by sytse 8y ago

   Interesting. Heroku had cold start issues when you were on the free tier and didn't have any questions for a couple of minutes. Did GAE work the same?
6. 846.▲
   by sytse 8y ago

   Thanks for sharing your perspective. I wonder if App developers where not ready since they did embrace Heroku.
7. 847.▲
   by sytse 8y ago

   So far everyone I meet that uses it production is using Lambda. It might be because they want to consume it as a SaaS. But maybe a self-managed solution would have to be compatible with Lambda to gain adoption. Of course self-hosted is more
8. 848.▲
   by sytse 8y ago

   The trend is to have applications use less memory. On bare metal an application used all memory, a virtual machine has the OS overhead per application, on a container an application uses just one process, and with serverless even the proces
9. 849.▲
   by sytse 8y ago

   If you're an app developer you shouldn't need kubectl. AppOps should be as easy as Heroku but based on Kubernetes so you have a choice of providers and a graduation path of you need more customization. With GitLab Auto DevOps we t
10. 850.▲
    by sytse 8y ago

    If you host on GitLab and push to GitHub that is now open source https://about.gitlab.com/2018/05/22/gitlab-10-8-released/
11. 851.▲
    by sytse 8y ago

    I can see that colocated companies would require you to fly in for interviews. Maybe some are open to grouping the interviews on the same day.
12. 852.▲
    by sytse 8y ago

    We have vancancies for site reliability engineers and Go programmers. We used to hire people without Ruby experience to work on the Ruby codebase but it took significantly longer for them to be effective so we stopped doing that.
13. 853.▲
    by sytse 8y ago

    We use a static website. That way you can do a git blame to see what line was last updated when. And it allows for separating the change from the approver.
14. 854.▲
    by sytse 8y ago

    I think changing your LinkedIn location to San Francisco Bay area and explaining during the first call you intent to move there when you've found a job is acceptable to most companies. BTW we hire in 90% of the world at GitLab
15. 855.▲
    by sytse 8y ago

    Yes, a single Prometheus server can probably handle the scale of most SaaS applications.
16. 856.▲
    by sytse 8y ago

    Really great project. Instead of a fragile centralized approach Thanos embraced the federated nature of Prometheus. We see us using this for GitLab.com. I just discussed Thanos with Ben who works on the Prometheus project itself and who lea
17. 857.▲
    GitLab (YC W15), Remote-Only, Is Hiring Support Engineers and More(about.gitlab.com)

    1 points by sytse 8y ago
18. 858.▲
    by sytse 8y ago

    The OP linked to a set tweets from Joe Beda (author of Kubernetes) that read "When you create a complex deployment system with Jenkins, Bash, Puppet/Chef/Salt/Ansible, AWS, Terraform, etc. you end up with a unique brand
19. 859.▲
    by sytse 8y ago

    I think that working full-time from home is hard in a firm where the leadership is at the HQ. If everyone is remote you no longer miss out by working from home.
20. 860.▲
    by sytse 8y ago

    Sometimes the best people live in a more expensive location.
21. 861.▲
    by sytse 8y ago

    Our rates indeed resemble cost of living a lot. We've found that the rent was a good indicator of market rate https://about.gitlab.com/handbook/people-operations/global-c...
22. 862.▲
    by sytse 8y ago

    For our compensation principles please see https://about.gitlab.com/handbook/people-operations/global-c... We don't think cost of living make sense. We do think paying market rates is the way to go. Market ra
23. 863.▲
    by sytse 8y ago

    Awesome, thanks for the overview.
24. 864.▲
    by sytse 8y ago

    The operator framework seems really useful. Do you expect that eventually it or something like it will become part of Kubernetes?
25. 865.▲
    by sytse 8y ago

    The advantage is that if one storage nose is offline the rest of the site can still function. Spokes is more elaborate can can deal with node failure. We plan to rely on cloud storage so we can quickly attach a new VM with Gitaly.
26. 866.▲
    by sytse 8y ago

    We're working towards Gitaly 1.0 that would allow you to run GitLab without NFS. This isn't HA but it would prevent one NFS server from taking down the whole cluster.
27. 867.▲
    by sytse 8y ago

    Because the Rails application server is currently single threaded it forks multiple processes that each take up about half a gigabyte of RAM. Running fewer processes would cause increased latency for users.
28. 868.▲
    by sytse 8y ago

    Thanks, you can indeed do HA this way. When Gitaly 1.0 lands you won't have to mount the NFS volumes on the application servers anymore as everything will go over gRPC.
29. 869.▲
    by sytse 8y ago

    Thanks for posting. HA is a paid feature of GitLab and will likely stay a paid feature. We're working hard on a cloud native alternative to the docker container that works well on Kubernetes. There is more information on https:/&
30. 870.▲
    by sytse 9y ago

    My bad, thanks for the hint.