Re: plugins,caches, startup time

2016-09-30 Thread Aleix Pol
On Sat, Oct 1, 2016 at 12:18 AM, Sebastian Kügler wrote: > On Friday, September 30, 2016 4:23:52 PM UTC Aleix Pol wrote: >> > Nice, I suppose KPackages are a little different to plugins, since there's >> > more overhead reading, the package metadata is stored as .desktop file, >> > which means mor

Re: plugins,caches, startup time

2016-09-30 Thread Sebastian Kügler
On Friday, September 30, 2016 10:18:21 PM UTC Sebastian Kügler wrote: > > My suggestion is to first get the type system right in > > plasma-framework then we look into enforcing caches. I'm especially > > afraid of this one as it will require quite a lot of work from the > > packagers. > > Furtherm

Re: plugins,caches, startup time

2016-09-30 Thread Sebastian Kügler
On Friday, September 30, 2016 4:23:52 PM UTC Aleix Pol wrote: > > Nice, I suppose KPackages are a little different to plugins, since there's > > more overhead reading, the package metadata is stored as .desktop file, > > which means more conversion costs compared to the binary json that's in > > th

Re: plugins,caches, startup time

2016-09-30 Thread Aleix Pol
On Fri, Sep 30, 2016 at 2:35 PM, Sebastian Kügler wrote: > Hi, > > On Tuesday, September 27, 2016 4:52:22 PM UTC Marco Martin wrote: >> as there is being some work in plugin caching right now, to see if /what we >> can save at startup time would be nice if different people on different >> systems

Re: plugins,caches, startup time

2016-09-30 Thread Sebastian Kügler
Hi, On Tuesday, September 27, 2016 4:52:22 PM UTC Marco Martin wrote: > as there is being some work in plugin caching right now, to see if /what we > can save at startup time would be nice if different people on different > systems do some tests. > on his system, by indexing plugins Sebas saves ab

Re: plugins,caches, startup time

2016-09-28 Thread Marco Martin
On Wednesday 28 September 2016 22:23:15 Alexander Potashev wrote: > 2016-09-27 17:52 GMT+03:00 Marco Martin : > > 2-300 milliseconds > > Marco, > > Is that > - 2.3 ms, > - 2.3 seconds or > - a range from 2 ms through 300 ms? 200-300 i mean -- Marco Martin

Re: plugins,caches, startup time

2016-09-28 Thread Alexander Potashev
2016-09-27 17:52 GMT+03:00 Marco Martin : > 2-300 milliseconds Marco, Is that - 2.3 ms, - 2.3 seconds or - a range from 2 ms through 300 ms? -- Alexander Potashev

Re: plugins,caches, startup time

2016-09-27 Thread David Edmundson
On Tue, Sep 27, 2016 at 9:32 PM, Eike Hein wrote: > Worth keeping in mind that "it's only 300 msecs" adds up though, > 300 msecs here, 300 msecs there ... also it's a question of "do > we expect this cost point to become worse over time?", i.e. if > nothing it done it might not stay at 300 msecs.

Re: plugins,caches, startup time

2016-09-27 Thread Eike Hein
Worth keeping in mind that "it's only 300 msecs" adds up though, 300 msecs here, 300 msecs there ... also it's a question of "do we expect this cost point to become worse over time?", i.e. if nothing it done it might not stay at 300 msecs. Cheers, Eike

plugins,caches, startup time

2016-09-27 Thread Marco Martin
Hi all, as there is being some work in plugin caching right now, to see if /what we can save at startup time would be nice if different people on different systems do some tests. on his system, by indexing plugins Sebas saves about 2-300 milliseconds. How did you test that, so that we see wether