Bug 349358 - Lag on first opening of plasma elements like menu, calendar, network (see video)
Summary: Lag on first opening of plasma elements like menu, calendar, network (see video)
Status: CLOSED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.3.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-18 23:45 UTC by jeremy9856
Modified: 2016-08-20 20:31 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Lag on first opening of plama elements (1.26 MB, video/x-matroska)
2015-06-18 23:46 UTC, jeremy9856
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jeremy9856 2015-06-18 23:45:47 UTC
I made a little video to show you that first opening of plama elements like menu, calendar, network is slow, have a lag. The others times you open these elements it's fast.

Reproducible: Always

Steps to Reproduce:
1. Open a plama elements like menu, calendar, network

Actual Results:  
lag on first opening

Expected Results:  
fast opening
Comment 1 jeremy9856 2015-06-18 23:46:14 UTC
Created attachment 93229 [details]
Lag on first opening of plama elements
Comment 2 David Edmundson 2015-06-19 02:57:43 UTC
The first time you open it has to load all the files and compile the JS. We do loading on demand to save memory.

We are constantly improving performance, 5.4 will bring a huge boost, so we don't need a specific bug report on this as it will always be improvable.
Comment 3 jeremy9856 2015-06-19 09:43:46 UTC
Ok I hope we can achieve the speed of plasma 4.
By the way why there is a such difference between plasma 4 and 5 ?
Comment 4 Artur O. 2015-09-03 03:12:34 UTC
(In reply to David Edmundson from comment #2)
> The first time you open it has to load all the files and compile the JS. We
> do loading on demand to save memory.
> 
> We are constantly improving performance, 5.4 will bring a huge boost, so we
> don't need a specific bug report on this as it will always be improvable.

Would it be possible to compile it before for people with memory or maybe some cache?
Comment 5 jeremy9856 2015-09-03 05:47:13 UTC
I agree, it's still really slow on first openning on plasma 5.4
Comment 6 jeremy9856 2015-09-09 08:03:30 UTC
I tested again Kubuntu 15.10 with plasma 5.4 on a hard install and it's very very slow.
The memory saved is about 50MB and I don't think it worth it, especially on system with 3GB or more.

Everything feel fast on Plasma 5.4 except that.
Comment 7 jeremy9856 2015-09-12 08:56:37 UTC
I'm sorry to insist with that but can we have a feedback please ?
Thank you
Comment 8 David Edmundson 2015-09-12 09:37:59 UTC
>I'm sorry to insist with that but can we have a feedback please ?

We are constantly improving performance. 

It doesn't help to have this as a bug report because it's something we're always improving, it's split over multiple places and there's never a point where it's "done".
Comment 9 jeremy9856 2015-09-12 09:45:02 UTC
Ok but what about preloading all the needed plasmoids to avoid the need to load all the files and compile the JS at the moment you first click on it ?

I don't know how it works on plasma 4 but it's fast and it should be at least as fast on the new version of plasma. I would even say that on this next gen plasma it should be faster.
Comment 10 jeremy9856 2015-11-05 09:49:43 UTC
David, any update on this please ?
Thank you
Comment 11 David Edmundson 2015-11-05 14:50:23 UTC
No. Sorry
Comment 12 jeremy9856 2015-11-23 20:48:40 UTC
David,

Is it possible to add an option to preload all the needed plasmoids and avoid the need to load all the files and compile the JS at the moment you first click on it please ?

I think that if the user have a powerful computer, want it to be reactive and there is no technical diificulties, he should be able do to it. Don't you think ?

Thanks
Comment 13 jeremy9856 2015-11-26 12:32:31 UTC
I just checked again on Manjaro and the memory saved by not loading some Plasma elements is totally irrelevant. A few MB at most at the price of a really bad first impression and God know that KDE don't need that. 

I think an option to choose to load everything in memory is even not needed at all. We should load everything by default. I can't understand why a such decision as been made ! Please David, please !
Comment 14 jeremy9856 2015-12-10 11:03:33 UTC
David, I don't want to be annoying but honnestly loading all the files and compile the JS at the first opening to save memory is not a good idea. You said that 5.4 will bring a huge boost but that is not the case. When I click on the clock to display the calendar on my Core i3 w/ SSD almost 2 seconds pass before the calendar is displayed. Every first click on the plasmoids is frustrating. That's insane.

Please make plasma load everything on boot or at least give us the option to choose.

Thank you a lot for your work.
Comment 15 jeremy9856 2015-12-14 14:30:09 UTC
David have you listen the last Linux Action Show 395 ? They have the same feeling about the desktop. It can be felt sluggish on the first elements opening :

https://youtu.be/E02gHmG61ro?t=55m00s
https://youtu.be/E02gHmG61ro?t=1h8m25s

Again that make bad press and bad feeling about the Plasma 5 desktop for nothing...
Comment 16 jeremy9856 2015-12-19 11:14:59 UTC
David, I will be happy if you can give us your thought here
https://forum.kde.org/viewtopic.php?f=289&t=130131
Comment 17 jeremy9856 2016-01-05 14:31:00 UTC
I just tested, for fun, the Nouveau drivers and Plasma 5 is much faster !
It's not as fast as Plasma 4 but it's maybe 2 or 3 times faster than with the Nvidia driver.
The lag on first click is not gone but it's very little now (except with the calendar plasmoid).
Comment 18 jeremy9856 2016-08-20 20:31:09 UTC
I'm thinking using KDE again so I wonder if you have changed your mind David to add the possibility to load every needed plasmoid ?
Thanks !