Poor performance on large resolution

[OliverJAsh]

Version: VSCode Insiders.
Latest OS X

I have a secondary monitor plugged into my MacBook pro which has 3840 x 2160 pixels. I have my resolution set to 2560 x 1440.

When I resize vscode to use the full size of the screen, there is about ~300ms - ~500ms of lag when editing a medium size file (~300 LOC in a TypeScript file). I haven't tried to compare this performance with smaller and larger files, however I have noticed that editing an empty file is much faster.

I'm not sure how I can provide more information, but do let me know if you need anything else.

[jayphelps]

On my 4K, 3840x2160 monitor when the window is full width/height:

(these are just spit-balled timings, not from profiling)

• Start up until able to type in new file: about 8 seconds.
• New file is about 1 sec.
• Typing has a noticeable lag, but less than a 1 sec.

For comparison, Sublime 3 takes less than 1 sec to start, no discernible delay in creating new files or typing. (It used to have the same problem, but they obv fixed it)

[jayphelps]

Because my timings were just guesses, I recorded a bunch of Timeline profiles for you to get more accurate info from.

I'm not sure if it's possible to record a Timeline of the entire start up process. The closest thing I can think of is just using ⌘+R inside the Timeline, which seemingly does a soft refresh.

I've recorded that along with creating a new file and typing.

timelines.zip

[bpasero]

@OliverJAsh maybe you could also attach some profile traces?

[OliverJAsh]

Sure, I would be happy to help! Do you mean a timeline recording? How do I
do that?

On Fri, 5 Aug 2016 at 16:24 Benjamin Pasero notifications@github.com
wrote:

@OliverJAsh https://github.com/OliverJAsh maybe you could also attach
some profile traces?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#9432 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4QCcWoUlD0cGC8GL0CtIDW1gQdis6aks5qc1W6gaJpZM4JOl4_
.

[bpasero]

Profile would be great:

[OliverJAsh]

I'm not quite sure how to open the dev tools from within the app? I'm not running Electron?

[bpasero]

@OliverJAsh Help > Toggle Developer Tools should do it 👍

[OliverJAsh]

@bpasero Here's the CPU profile you requested, hope it helps :-) Anything else I can do to help? I would love to help fix this CPU-20160811T144733.cpuprofile.zip

[bpasero]

Thanks for the trace, I do not see anything suspicious though, so the time is not spend in any of our code it seems, rather likely in the rendering in Chrome.