Re: GitLab migration status and roadmap

[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.

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 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.
>
> That was a couple of seconds for me no cache involved whatsoever. I am
> pretty sure our numbers are GNOME infra related.
>
> Nonetheless we will reach out to GitLab to see if there are best
> practices for deployments performance+scalability.
>
> > But I tested that URL twice more with Ctrl+F5 and
> > got only 3 and 4 seconds, respectively. So it's inconsistent and not
> always
> > so slow. But even this is much, much slower than current git.gnome.org
> (<1
> > second).
> >
> > I don't expect GitLab to be as fast as cgit. 3-4 seconds seems like a
> > reasonable trade-off in exchange for the new features that GitLab brings.
> > But 17 seconds or 28 seconds is obviously not OK.
> >
> > Michael
> >
> >
> > ___
> > desktop-devel-list mailing list
> > desktop-devel-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
>
>
> --
> Cheers,
> Alberto Ruiz
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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. Wy too long. That suggests it's not
> a GNOME hosting problem.

That was a couple of seconds for me no cache involved whatsoever. I am
pretty sure our numbers are GNOME infra related.

Nonetheless we will reach out to GitLab to see if there are best
practices for deployments performance+scalability.

> But I tested that URL twice more with Ctrl+F5 and
> got only 3 and 4 seconds, respectively. So it's inconsistent and not always
> so slow. But even this is much, much slower than current git.gnome.org (<1
> second).
>
> I don't expect GitLab to be as fast as cgit. 3-4 seconds seems like a
> reasonable trade-off in exchange for the new features that GitLab brings.
> But 17 seconds or 28 seconds is obviously not OK.
>
> Michael
>
>
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Cheers,
Alberto Ruiz
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 faster? I can 
definitely feel it slower than previous weeks, in general.


I tested our instance again, 
https://gitlab.gnome.org/GNOME/json-glib/commits/master. It was 26 
seconds, compared to 28 seconds on my first attempt earlier today. I 
pressed Ctrl+F5 and the page loaded in 4 seconds. I pressed Ctrl+F5 yet 
again and the page loaded in 5 seconds.


Michael

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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, Aug 14, 2017 at 11:55 PM, Michael Catanzaro <
mike.catanz...@gmail.com> wrote:

> 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 URL twice more with Ctrl+F5
> and got only 3 and 4 seconds, respectively. So it's inconsistent and not
> always so slow. But even this is much, much slower than current
> git.gnome.org (<1 second).
>
> I don't expect GitLab to be as fast as cgit. 3-4 seconds seems like a
> reasonable trade-off in exchange for the new features that GitLab brings.
> But 17 seconds or 28 seconds is obviously not OK.
>
> Michael
>
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 URL twice more with 
Ctrl+F5 and got only 3 and 4 seconds, respectively. So it's 
inconsistent and not always so slow. But even this is much, much slower 
than current git.gnome.org (<1 second).


I don't expect GitLab to be as fast as cgit. 3-4 seconds seems like a 
reasonable trade-off in exchange for the new features that GitLab 
brings. But 17 seconds or 28 seconds is obviously not OK.


Michael

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Build system change GTK's master branch

[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 now has a build-time dependency on:

  - Python 3.x
  - Meson - http://mesonbuild.com
  - Ninja (though Meson also supports Visual Studio out of the box)

Building GTK+ is now a matter of calling:

  $ meson $builddir $srcdir
  $ ninja -C $builddir
  $ sudo ninja -C $builddir install

(where $builddir is the build directory you want to use, and $srcdir
is the directory with the GTK+ sources)

The main change is that now GTK+ takes about ⅓ of the time to build
compared to the Autotools build, with likely bigger wins on older/less
powerful hardware; the Visual Studio support on Windows should be at
least a couple of orders of magnitude easier (shout out to Fan
Chun-wei for having spent so, so many hours ensuring that we could
even build on Windows with Visual Studio and MSVC); and maintaining
the build system should be equally easier for everyone on any platform
we currently support.

Of course no migration is going to be perfect at the first try, even
though we have been building GTK+ master using Meson on the GNOME
continuous integration pipeline for a while, now. Please, report any
issue you may find.

Additionally, the following dependencies of GTK+ have added a Meson
build side-by-side with Autotools:

  - GLib
  - Pango
  - GdkPixbuf
  - ATK
  - libepoxy

There are no plans for using Meson exclusively, or even side-by-side
with Autotools, on the 2.24 and 3.22 branches — at least for the
foreseeable future.

Ciao,
 Emmanuele.

-- 
https://www.bassi.io
[@] ebassi [@gmail.com]
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 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. cgit shows wy more commits per page.
> >
> > So... yeah.
>
> Yeah, that's what I meant. Takes ~20-30s to load the commit list of
> gexiv2 or json-glib, and just opening the overview page of a project
> also takes ~10s.
>
> But as Bastien also said, bugzilla has grown a bit slow since some time
> as well. cgit is still fast, though.
>
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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. cgit shows wy more commits per page.
> 
> So... yeah.

Yeah, that's what I meant. Takes ~20-30s to load the commit list of
gexiv2 or json-glib, and just opening the overview page of a project
also takes ~10s.

But as Bastien also said, bugzilla has grown a bit slow since some time
as well. cgit is still fast, though.

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 our cgit the page loads in maybe half a 
second. cgit shows wy more commits per page.


So... yeah.

Michael

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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,
> 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 at 11:18, Richard Hughes  wrote:
> > 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
> > https://gitlab.gnome.org/GNOME/json-glib -- is the machine hosting the
> > GitLab instance a proper server in a datacenter somewhere or is the
> > demo being run from a test machine under someones desk? I don't want
> > people's first reaction to be "this is kinda slow".
> >
> > Richard.
> > ___
> > desktop-devel-list mailing list
> > desktop-devel-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
>
>
> --
> https://www.bassi.io
> [@] ebassi [@gmail.com]
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 at 11:18, Richard Hughes  wrote:
> 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
> https://gitlab.gnome.org/GNOME/json-glib -- is the machine hosting the
> GitLab instance a proper server in a datacenter somewhere or is the
> demo being run from a test machine under someones desk? I don't want
> people's first reaction to be "this is kinda slow".
>
> Richard.
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
https://www.bassi.io
[@] ebassi [@gmail.com]
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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
https://gitlab.gnome.org/GNOME/json-glib -- is the machine hosting the
GitLab instance a proper server in a datacenter somewhere or is the
demo being run from a test machine under someones desk? I don't want
people's first reaction to be "this is kinda slow".

Richard.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 means projects that go into our real
> > deployment at gitlab.gnome.org [1] are still manually added and
> > they
> > have to request us to join. We had have many projects and
> > maintainers
> > asking us to move, but as said to you individually we are holding
> > the
> > gates until we fix our remaining blockers.
> 
> 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.

To be fair, Bugzilla used to be instant and now takes around 10 seconds
to show a page from Europe. So it might be something more general than
Gitlab.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

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

[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 make
> > > your 
> > > changes to git master for 3.27/3.28.
> > > 
> > > Please do continue to fix bugs in the meson build for your
> > > modules.
> > 
> > Thanks Jeremy! This is a good rule to follow.
> > 
> > I do encourage projects to remove their Autotools build systems as
> > soon 
> > as reasonable, since having to support two build systems is
> > causing 
> > many problems. But it's probably not reasonable to do so at this
> > point 
> > until after you've first branched for gnome-3-26.
> 
> Related to this, when migrating your module, please do keep in mind
> that
> Damned Lies support for Meson modules is still incomplete, see
> https://bugzilla.gnome.org/show_bug.cgi?id=783099.
> 
> As Piotr reported elsewhere [1], totem-pl-parser, nautilus-sendto,
> and
> gnome-bluetooth have broken/incomplete i18n support as a result.

The pot file in those haven't changed since autotools, so the i18n
support should be as it was, unless damned-lies can't use the cached
version of the pot files.

> Your help with fixing #783099 would be much appreciated.
> 
> Thanks,
> pk
> 
> [1] https://mail.gnome.org/archives/gnome-i18n/2017-August/msg00015.h
> tml
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab migration status and roadmap

[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 manually added and they
have to request us to join. We had have many projects and maintainers
asking us to move, but as said to you individually we are holding the
gates until we fix our remaining blockers.


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.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list