Re: GitLab migration status and roadmap

[Hashem nolastname]

I've deployed a docker gitlab instance for my workplace. We also struggled
with poor performance.
Gitlab 9.5 has made things noticeably better. What also helped greatly was
increasing the RAM allocated to the machine.

On Fri, Aug 25, 2017 at 10:45 AM, Carlos Soriano  wrote:

> Just a quick update about performance. Seems their "performance team" is
> starting to bring some results, in the last release they report
> improvements in several places. You can take a look at
> https://about.gitlab.com/2017/08/22/gitlab-9-5-released/#performance-
> improvements
>
> Cheers,
> Carlos Soriano
>
> On Tue, Aug 15, 2017 at 5:54 PM, Olav Vitters  wrote:
>
>> On Fri, Aug 11, 2017 at 08:48:34PM +0200, Carlos Soriano wrote:
>> > Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools,
>> is
>> > up to the maintainer what to do with them.
>>
>> Note that this script has a lot of things it does NOT handle. As agreed
>> with Alberto I'm going to fork this into a better script.
>>
>> Basic things like:
>> - ensuring old bugs correctly link to new bugs (bugzilla 123 -> github
>>   something)
>> - links from existing comments to other bugs (comment specifying
>>   bugzilla 123... which now could be anywhere)
>> - migrate users
>> - ensure users still get notifications on their open bugs
>> - what to do with e.g. keywords
>>
>> are not handled by the current script.
>>
>> Note this is not a complaint as I agreed to work on this.
>>
>> --
>> Regards,
>> Olav
>>
>
>
> ___
> 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

[Carlos Soriano]

Just a quick update about performance. Seems their "performance team" is
starting to bring some results, in the last release they report
improvements in several places. You can take a look at
https://about.gitlab.com/2017/08/22/gitlab-9-5-released/#performance-improvements

Cheers,
Carlos Soriano

On Tue, Aug 15, 2017 at 5:54 PM, Olav Vitters  wrote:

> On Fri, Aug 11, 2017 at 08:48:34PM +0200, Carlos Soriano wrote:
> > Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools,
> is
> > up to the maintainer what to do with them.
>
> Note that this script has a lot of things it does NOT handle. As agreed
> with Alberto I'm going to fork this into a better script.
>
> Basic things like:
> - ensuring old bugs correctly link to new bugs (bugzilla 123 -> github
>   something)
> - links from existing comments to other bugs (comment specifying
>   bugzilla 123... which now could be anywhere)
> - migrate users
> - ensure users still get notifications on their open bugs
> - what to do with e.g. keywords
>
> are not handled by the current script.
>
> Note this is not a complaint as I agreed to work on this.
>
> --
> Regards,
> Olav
>
___
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

[Olav Vitters]

On Fri, Aug 11, 2017 at 08:48:34PM +0200, Carlos Soriano wrote:
> Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools, is
> up to the maintainer what to do with them.

Note that this script has a lot of things it does NOT handle. As agreed
with Alberto I'm going to fork this into a better script.

Basic things like:
- ensuring old bugs correctly link to new bugs (bugzilla 123 -> github
  something)
- links from existing comments to other bugs (comment specifying
  bugzilla 123... which now could be anywhere)
- migrate users
- ensure users still get notifications on their open bugs
- what to do with e.g. keywords

are not handled by the current script.

Note this is not a complaint as I agreed to work on this.

-- 
Regards,
Olav
___
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]

And "that was a couple of seconds for me no cache involved whatsoever"
was for gitlab.com

2017-08-15 2:38 GMT+01:00 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.
>



-- 
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: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

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: 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

Re: GitLab migration status and roadmap

[Tobias Mueller]

Hi.

On Fr, 2017-08-11 at 14:37 +0200, Carlos Soriano wrote:
> Also I hope in the time frame of 3-4 months the pilot program is successful
For completeness sake:
Are we still considering to *not* move to Gitlab if that pilot is not
successful?

How do we measure "success"?

Cheers,
  Tobi
___
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]

Yeah I guess, when the full migration is done, if the maintainer wants to
migrate the bugs, we will use that tool.

On Sat, Aug 12, 2017 at 4:48 PM, Sébastien Wilmet  wrote:

> On Fri, Aug 11, 2017 at 08:48:34PM +0200, Carlos Soriano wrote:
> > Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools,
> is
> > up to the maintainer what to do with them.
>
> OK, and when the full migration will be done for all GNOME modules, do
> you already know if that script will be used to migrate the bugzilla as
> well? And then making the bugzilla read-only?
>
> --
> Sébastien
> ___
> 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

[Sébastien Wilmet]

On Fri, Aug 11, 2017 at 08:48:34PM +0200, Carlos Soriano wrote:
> Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools, is
> up to the maintainer what to do with them.

OK, and when the full migration will be done for all GNOME modules, do
you already know if that script will be used to migrate the bugzilla as
well? And then making the bugzilla read-only?

--
Sébastien
___
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]

Bugs can be migrated with https://gitlab.com/aruiz/gitlab-gnome-tools, is
up to the maintainer what to do with them.

Best,
Carlos Soriano

On Fri, Aug 11, 2017 at 5:06 PM, Sébastien Wilmet  wrote:

> On Fri, Aug 11, 2017 at 02:37:41PM +0200, Carlos Soriano wrote:
> > As usual, feel free to ask any questions in this thread or personally to
> > Alberto Ruiz or me, we are happy to answer.
>
> Are all the bugs on bugzilla also migrated when a module moves to
> GitLab? How is that handled currently?
>
> --
> Sébastien
> ___
> 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

[Sébastien Wilmet]

On Fri, Aug 11, 2017 at 02:37:41PM +0200, Carlos Soriano wrote:
> As usual, feel free to ask any questions in this thread or personally to
> Alberto Ruiz or me, we are happy to answer.

Are all the bugs on bugzilla also migrated when a module moves to
GitLab? How is that handled currently?

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