GitLab Create Editor Group, 16 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Create:Editor - VS Code/Web IDE Demo Part 3: Performance

Description

Paul Slaughter, Staff FE Engineer, and Eric Schurter, Sr. Product Manager, demo a proof of concept implementation of VS Code running in the web, replacing the GitLab Web IDE.

Part 3 is focused on the the performance benefits of VS Code over the current Web IDE.

Learn more here: https://gitlab.com/gitlab-org/gitlab/-/issues/345718

A

Okay, welcome back to part three of our vs code demo. We have uh a focus right now on performance.

A

One of the things we know about our current web ide is that when you open up extremely large repositories or large, mrs you have to sit there and wait a little while so I'm going to put you on the spot paul and ask if you have a very large repository or test case that you can try and load, maybe one live, and then one on on your local environment.

B

Let's, let's do one on dot com, let's load the gitlabproject.com.

A

I'm gonna get my timer ready. It won't be on the recording, but you have to trust me that I'm recording I'm timing as best as.

B

Stop watch tell me when to go.

A

Okay, ready set, go.

B

Okay, there we go, uh I think we can also look at.

B

Is the id on here? This is not the amount of memories taking. I don't know why it's it's full of lies.

A

That was nine seconds give or take with a little bit of latency, for example,.

B

The amount of memory this takes, though too, is is quite large. Let me see if I can take a snapshot.

B

And it's because of loading the file tree. We have architectural issues that just cause a massive amount of watchers to be set for every little part of the file tree and for large projects. It's a lot uh yeah.

A

I can hear your fans too.

B

I know no might kick me out.

B

uh While that's taking the snapshot, uh let's see, if we can, uh let's see how quickly this will load up all.

A

Right ready set, go.

A

That was five seconds give or take.

B

A

B

I'm taking a snapshot over here so and.

A

You're and you're, using them I'm taking this one so so, potentially a reduction of half a hundred percent or fifty percent. I guess I should say, but um that's a that's, an impressive there's. Your memory heap.

B

Yeah so the fact this took very sh small amount of time to load yeah. There.

A

B

A

Oh, my goodness, look at that almost a gig of memory 864 for those that don't want to squint on the recording, 864.03 megabytes versus 134.

B

This is with no open files.

A

B

Or anything like that, wow so well,.

A

It's impressive nah, the performance benefits of vs code are pretty clear and, as we um discussed in various formats uh and issues right now, we'll keep pushing on this and profile it more in more detail and share with everybody. But that was a great demo.

B

Awesome much better, nothing.

A

Like shaving off half half the startup time, that's great.

B

A

All right well part: four, we can um tease is going to be about extending the usefulness of vs code and using custom editors and web views, and things like that so tune in for how far we can push vs code to make it feel more, get lab or even better.