News for hackers. Stuff that matters.
Re:Treating performance as a product: The technical story of... by twobyfour on Tuesday August 29, 2017 @04:53PM (#15127513)
It doesn't happen all the time - seems to be intermittent, but when it's happening, it'll go on for several minutes at a time. When it does happen, the activity monitor shows the browser process using basically the entire CPU.

Sometimes but not always, reloading the page fixes the problem; it does seem to be more likely to happen when the page has been open for an extended period, but sometimes the problem persists after a fresh page load. (There's one project that I use to organize most of my work, and I'm liable to leave that tab open to that project without reloading or even changing the sort/filter for weeks on end.)

Re:Treating performance as a product: The technical story of... by pspeter3 on Tuesday August 29, 2017 @04:56PM (#15127540)
Thanks for the detail! Your description makes me wonder if there is a lurking memory leak.
Re:Treating performance as a product: The technical story of... by twobyfour on Wednesday August 30, 2017 @08:42AM (#15131594)
What seems to happen is that memory usage spikes (by as much as 100 MB) alongside CPU usage while the typing lag is occurring, and then it drops back to baseline as soon as the text is displayed properly.
Re:Treating performance as a product: The technical story of... by twobyfour on Tuesday August 29, 2017 @05:01PM (#15127570)
Memory usage seems pretty stable, but I'll make a note to check that next time the issue occurs.