3 ms·
I enjoy hearing people comment on their own "terrible" design decisions, though they never seem as bad as some of my own. :) Regarding performance, did anyone
by baddox 12y ago
I enjoy hearing people comment on their own "terrible" design decisions, though they never seem as bad as some of my own. :)
Regarding performance, did anyone else have absolutely awful frame rates when zooming? On my beefy Macbook Pro in Chrome it would drop to two or three frames per second.
Edit: and on my Windows PC in Chrome, which was fairly beefy three years ago, it's more like a frame every few seconds.
- simoncion 12y agoI had no slowdowns while zooming on both my seven-ish-year-old Toughbook CF-30 and my three or four-year-old desktop machine. Chromium 38 on Linux on both.
- aroch 12y agoDisable "Enable zero-copy rasterizer" in chrome and give it another try. Its likely hitting the integrated graphics and not discrete or CPU, leading to the less than awesome FPS
- ceras 12y agoZooming on my x86 Chromebook was ~1fps or worse.
- deleted 12y ago[deleted]
- chromakode 12y agoIf the code detects that rendering a frame takes a while, it increases the threshold in which sub-panels are drawn. Hopefully it should speed up after those first couple frames.
- baddox 12y agoI must have gone at least 20 levels deep and it never noticeably improves.
- jfindley 12y agoMe too - it's much more interesting to read about terrible decisions, why they were made, etc than it is to read yet another unblemished story of success. We as an industry should be better at sharing "Hey, I did this wrong because X" stories, they are both interesting and useful.