Please see Sid's comment at https://news.ycombinator.com/item?id=18443014. The numbers are from two separate points in time.

Fair.

Sorry for the delay. Due to the spike in imports things are a bit backed up. Your import should be in the queue and will run eventually. As someone else mentioned it can take a lot of time to import, in general, depending on the number of issues, PRs, etc. Contact @movingtogitlab if you continue to have trouble.

GitLab.com offers private repos with unlimited users/collaborators for free. You even get 2,000 free CI minutes per month per group.

Thanks for your concern. Everything on https://monitor.gitlab.net is for public consumption. We're very transparent :)

Sorry about that. Was the 503 on GitLab.com (main application) or on the link in this discussion (monitor.gitlab.net)? The latter is to a public monitoring dashboard. It has been offline a couple of times today due to influx of traffic. We're closely monitoring it and attempting to keep it online. At the moment, GitLab.com itself has been absorbing the additional load, though. Let us know if you're seeing other issues.

I really like how the devs from gitlab are active on the HN thread and replying to people facing problems! Hardly see that with mature products anymore! Great going guys!

Sorry about that. We had to scale our monitoring dashboard due to increase in traffic.

No autoscaling in place? I can help :)

I like your idea. However, few performance problems are global. We have a public monitoring dashboard at https://monitor.gitlab.net/. Embedded in this dashboard are various metrics which will often show a drop in response time if we improve performance on a particular item. We usually find a page or set of pages that hit a particular bottleneck and improve that one point. Also, you will usually see mention of specific performance improvements in the changelog (https://gitlab.com/gitlab-org/gitlab-ce/raw/master/CHANGELOG...) and in our release blog posts.

I'm getting intermittent 502's\Bad Gateway errors here on your Grafana dashboard.

Other comments further down are showing other's are too. Hacker News Hug of death?

It's not a great look.

To be fair this is probably the first time the page has been hit by HN / Reddit simultaneously...

Yea, I'm working on that, will be deploying this nice caching proxy to speed up the dashboard.

Thanks to Comcast for creating Trickster.

https://github.com/Comcast/trickster

Never heard of Trickster till now, that's great.

Hope my post didn't come across as snarky as some others have... HN are like the Spanish Inquisition. No one expects.

Yea, I haven't used it myself, but the reports are that it works better than the original PromCache proxy. It's been on my TODO list for a while, but way lower on the priority list.

But you know, when the internet decides it's time for everyone to look at your site, some random new stuff might be better than serving 5xx all day. :-D

New HTTP error code:

HTTP 512 - Social Media induced DDOS due to media related frenzy :)

Good luck!

Thanks for the kind words. I'm glad you like the swag and enjoy using GitLab.

Thanks for your concern :) Many from our team are indeed on high alert.

Keep up the good work! The next few weeks could get interesting (:

This is your superbowl/worldcup/elections night/etc! Good luck!

Sorry about that. We had to scale our monitoring dashboard a bit. It's back up at the moment. GitLab.com is separate infrastructure, though, and we hope it remains online despite the added traffic :)