Slow UI navigation in Mac

Hi, I know that optimizations and tweaks are still being worked on in terms of speed and memory resources and of course this is still a TP. But this is about navigating on the browser itself. The UI is kinda laggy and sometimes slow in responding when clicking stuff. For example, when switching tabs or stacking them. I felt some speed improvements on Windows but it's still there. On mac though, it's more apparent. I'm using a late '13 rMBP Yosemite. Navigating thru all the options and buttons and all really felt sluggish. I hope you guys could do more optimizations in the UI front and the overall navigation of the browser. More power to you guys!

The lag is present on Windows and Linux too. And guess what? It's because they moved entire GUI to CSS. Yep. They render the UI as a website :lol: In terms of performance, no way this will ever be anywhere near to using native system controls…

The lag is present on Windows and Linux too. And guess what? It's because they moved entire GUI to CSS. Yep. They render the UI as a website :lol: In terms of performance, no way this will ever be anywhere near to using native system controls…

New Opera does something similar, and it has no lags. So quick rendering is possible, even with "UI as webpage." In old Opera, the UI was also rendered by the engine, using web technologies and it had no lags. So greater display efficiency is possible.

Early on in the discussions over Opera 15, they said they wrote the whole GUI in HTML. That's an awful lot like a web page.

Looks like my memory works properly

At the same time, we also wanted to give Opera a more native look and feel. And hence, taking also into account that native toolkits have evolved over the last 10 years (especially on Mac), we decided to build the whole UI with native code: we stripped away Chromium’s UI layer, and built it piece by piece from scratch — a big undertaking, and what you see today is just the beginning.

The lag is present on Windows and Linux too. And guess what? It's because they moved entire GUI to CSS. Yep. They render the UI as a website :lol: In terms of performance, no way this will ever be anywhere near to using native system controls…

I think this won't be an issue for most people using the browser just as long as performance improvements are made over time. I just wanted to let it out there.

Yeah I still remember Opera's statements regarding chromium and doing the UI from scratch. I know the Vivaldi team will do an amazing job even if it's bit by bit.

Speed Dial is, I think the one I most want to have speed/performance improvements. Even just hovering the mouse on thumbnail has some quite delays.

"At the same time, we also wanted to give Opera a more native look and feel. And hence, taking also into account that native toolkits have evolved over the last 10 years (especially on Mac), we decided to build the whole UI with native code: we stripped away Chromium’s UI layer, and built it piece by piece from scratch — a big undertaking, and what you see today is just the beginning.

At first, we also planned to build Speed Dial, Stash, Discover and so on with native code, but when seeing that the performance of our first functional web-based prototypes was excellent, we decided to go with a web-based (and hence cross-platform) UI for these parts instead. Indeed, you can open Web Inspector and see how they’re built."

Is there a way where you can ditch memory - tell paging that the pages held is no longer needed?
A way out now is to close it all - push the power button, and then make the OS restore it all. That releases GB of memory, and you can resume. In Linux you can set "memory pressure" - 0 to 100. There is something seriously wrong with swapping at the moment, it feels like you allocate shared memory that is never released, This goes for Chrome, Opera and Vivaldi - so is there a way to explicitely release memory?

Is there a way where you can ditch memory - tell paging that the pages held is no longer needed?
A way out now is to close it all - push the power button, and then make the OS restore it all. That releases GB of memory, and you can resume. In Linux you can set "memory pressure" - 0 to 100. There is something seriously wrong with swapping at the moment, it feels like you allocate shared memory that is never released, This goes for Chrome, Opera and Vivaldi - so is there a way to explicitly release memory?

Are you using any extensions that use toolbar buttons/menus? if so you may be seeing this nasty memory leak bug that effects chromium based browsers (every time the popup ui for an extension is used memory is allocated and never released):

The UI response times really improved from the recent snapshots. Speed Dial navigation is more bearable now. But there still some delays when switching between tabs, either using a mouse or the shortcut keys. Sometimes a 1 to 1.5 second delay. Which is a bit on the slow side.

For tab switching, it's not really lag per se but delay (what's the diff? xD). If you compare it with, let's say Chrome or Opera, once you click on another tab it's switches to it almost instantly.

Btw it's actually not just Mac but Windows machines as well. I tested the browser first on my Mac and later on on my Windows PC and laptops.

Regarding the others especially the Speed Dial and the overall UI, many users do feel they're a bit on the slow front but not SUPER slow. I got dozens of tabs open as well. It's not that the browser itself is slowing down. I'm talking about the time the UI reacts or loads something once you click tabs or anything. But don't get me wrong, this browser is fast overall. I guess it varies per person on what is "slow" or "fast".

It's still in pre-alpha stages so I know they'll do great performance optimizations in the future.

I'm really not seeing it happen to me, though. I'm not denying it's happening to you (and therefore probably to some others too), but it may be an interaction with some aspect of your system configuration. When I click another tab or cycle with ⌘4, the view switches to the next tab pretty much immediately, possibly before I've even had a chance to lift my finger from the button or key. If I hold down ⌘4, it cycles through 10 open tabs (whether maximized to 2880x1800 on the Retina display or maximized to 2560x1440 on an external Thunderbolt display) about once per second, so about 100ms per tab switch (with each page that flashes by showing up fully rendered).