Re: GitLab migration status and roadmap

2017-08-14 Thread Michael Catanzaro
On Mon, Aug 14, 2017 at 5:03 PM, Carlos Soriano wrote: Ok, I'm happy if the cache at least work and won't hit that hard on a daily basis. But it's true is weird, I can raise this concern and see where they are at. Just checking, did the second time in our instance went

Re: GitLab migration status and roadmap

2017-08-14 Thread Carlos Soriano
Ok, I'm happy if the cache at least work and won't hit that hard on a daily basis. But it's true is weird, I can raise this concern and see where they are at. Just checking, did the second time in our instance went faster? I can definitely feel it slower than previous weeks, in general. On Mon,

Re: GitLab migration status and roadmap

2017-08-14 Thread Carlos Soriano
Can you try with https://gitlab.com/gitlab-org/gitlab-ce/commits/master? It took me 1 second. On Mon, Aug 14, 2017 at 7:47 PM, Jens Georg wrote: > > > > Ah yes, this is slower than before, this was not the case with our > > > instances few weeks ago. > > > > > > I need to check

Build system change GTK's master branch

2017-08-14 Thread Emmanuele Bassi
Hi all; executive summary: the master branch of GTK+ now builds with Meson, and the Autotools build system files have been dropped. The documentation has been updated to reflect the new build system — as well as, in some cases, the past 10 years of development. The change means that GTK+ master

Re: GitLab migration status and roadmap

2017-08-14 Thread Michael Catanzaro
On Mon, Aug 14, 2017 at 2:08 PM, Carlos Soriano wrote: Can you try with https://gitlab.com/gitlab-org/gitlab-ce/commits/master? It took me 1 second. 17 seconds here on my first attempt. Wy too long. That suggests it's not a GNOME hosting problem. But I tested that

Re: GitLab migration status and roadmap

2017-08-14 Thread Alberto Ruiz
2017-08-14 22:55 GMT+01:00 Michael Catanzaro : > On Mon, Aug 14, 2017 at 2:08 PM, Carlos Soriano wrote: >> >> Can you try with https://gitlab.com/gitlab-org/gitlab-ce/commits/master? >> It took me 1 second. > > > 17 seconds here on my first attempt.

Re: GitLab migration status and roadmap

2017-08-14 Thread Carlos Soriano
Ok thanks for testing Michael. I just tested in Incognito Window and with different browsers and it was fast (2 secs). So it looks like it's random. I guess there is a bug around. On Tue, Aug 15, 2017 at 12:15 AM, Alberto Ruiz wrote: > 2017-08-14 22:55 GMT+01:00 Michael

Re: GitLab migration status and roadmap

2017-08-14 Thread Michael Catanzaro
On Mon, Aug 14, 2017 at 5:15 PM, Alberto Ruiz wrote: That was a couple of seconds for me no cache involved whatsoever. I am pretty sure our numbers are GNOME infra related. But that 17-second result was for gitlab.com, not for us.

Re: GitLab migration status and roadmap

2017-08-14 Thread Jens Georg
Hello all, As you may know we continue working and pushing for our transition from Bugzilla and cgit to GitLab. Similarly to what we said in the previous mail thread, we are still in the pilot program phase, that means projects that go into our real deployment at gitlab.gnome.org [1] are still

Re: GitLab migration status and roadmap

2017-08-14 Thread Carlos Soriano
Ah yes, this is slower than before, this was not the case with our instances few weeks ago. I need to check with Andrea. On Mon, Aug 14, 2017 at 12:25 PM, Emmanuele Bassi wrote: > Considering that large repos on gitlab.com — like, say, >

Re: Let's pause meson migration in preparation for the 3.26 release

2017-08-14 Thread Bastien Nocera
On Sun, 2017-08-13 at 20:42 +0200, Petr Kovar wrote: > On Fri, 11 Aug 2017 11:21:05 -0500 > Michael Catanzaro wrote: > > > On Fri, Aug 11, 2017 at 10:59 AM, Jeremy Bicha > > wrote: > > > If you want to do these things, please branch for 3.26 and

Re: GitLab migration status and roadmap

2017-08-14 Thread Richard Hughes
On 14 August 2017 at 10:02, Jens Georg wrote: > I'm currently massively underwhelmed by the overall performance and > snappiness of the web interface, even for a small project with not that > much commit history. Right; I also found that when sitting In London browsing

Re: GitLab migration status and roadmap

2017-08-14 Thread Bastien Nocera
On Mon, 2017-08-14 at 11:02 +0200, Jens Georg wrote: > > Hello all, > > > > As you may know we continue working and pushing for our transition > > from Bugzilla and cgit to GitLab. > > Similarly to what we said in the previous mail thread, we are still > > in > > the pilot program phase, that

Re: GitLab migration status and roadmap

2017-08-14 Thread Emmanuele Bassi
Considering that large repos on gitlab.com — like, say, https://gitlab.com/gitlab-org/gitlab-ce/commits/master — are faster than gitlab.gnome.org, I think the issue is on our end, unless GitLab's enterprise edition is more optimised than the community edition. Ciao, Emmanuele. On 14 August 2017

Re: GitLab migration status and roadmap

2017-08-14 Thread Michael Catanzaro
On Mon, Aug 14, 2017 at 5:29 AM, Carlos Soriano wrote: Ah yes, this is slower than before, this was not the case with our instances few weeks ago. I need to check with Andrea. I tried to load the commit log for json-glib (from North America) and it took 28 seconds. With

Re: GitLab migration status and roadmap

2017-08-14 Thread Jens Georg
> > Ah yes, this is slower than before, this was not the case with our  > > instances few weeks ago. > > > > I need to check with Andrea. > > I tried to load the commit log for json-glib (from North America) > and  > it took 28 seconds. With our cgit the page loads in maybe half a  > second.