Re: Plugin locator performance ballpark

2013-09-10 Thread David Faure
On Monday 09 September 2013 17:10:25 Martin Graesslin wrote: > On Monday 09 September 2013 16:48:05 David Faure wrote: > > On Monday 09 September 2013 14:23:10 Sebastian Kügler wrote: > > > Martin Grässlin asked if we could offer an async API for this. Opinions? > > > > This task is mostly I/O, an

Re: Plugin locator performance ballpark

2013-09-09 Thread David Faure
On Monday 09 September 2013 14:23:10 Sebastian Kügler wrote: > Martin Grässlin asked if we could offer an async API for this. Opinions? This task is mostly I/O, and a bit of CPU. Portable async I/O requires doing it in a thread. To avoid setting up a thread every time, this could use QThreadPool (

Re: Plugin locator performance ballpark

2013-09-09 Thread Martin Graesslin
On Monday 09 September 2013 16:48:05 David Faure wrote: > On Monday 09 September 2013 14:23:10 Sebastian Kügler wrote: > > Martin Grässlin asked if we could offer an async API for this. Opinions? > > This task is mostly I/O, and a bit of CPU. > Portable async I/O requires doing it in a thread. > T

Re: Plugin locator performance ballpark

2013-09-09 Thread Sebastian Kügler
On Sunday, September 08, 2013 11:17:56 David Faure wrote: > On Thursday 05 September 2013 01:04:52 Sebastian Kügler wrote: > > Reading just $PLUGINS/kf5, 52 plugins > > > > 21893.0 microsec (KServiceTypeTrader) > > 95835.0 microsec (Metadata) > > > > --> Reading metadata is 4-5 slower, ~100ms >

Re: Plugin locator performance ballpark

2013-09-08 Thread Boudewijn Rempt
On Sun, 8 Sep 2013, Boudewijn Rempt wrote: I like the directoryname idea, and actually, I'd go for a hierarchy: calligra/filter calligra/parts calligra/words calligra/krita/paintop calligra/krita/filter calligra/krita/extensions etcetera. that should limit the number of plugins per directory

Re: Plugin locator performance ballpark

2013-09-08 Thread Boudewijn Rempt
On Sun, 8 Sep 2013, David Faure wrote: On Thursday 05 September 2013 01:04:52 Sebastian Kügler wrote: Reading just $PLUGINS/kf5, 52 plugins 21893.0 microsec (KServiceTypeTrader) 95835.0 microsec (Metadata) --> Reading metadata is 4-5 slower, ~100ms Reading $PLUGINS recursively, 127 plugins

Re: Plugin locator performance ballpark

2013-09-08 Thread Alexander Neundorf
On Sunday 08 September 2013, David Faure wrote: > On Thursday 05 September 2013 01:04:52 Sebastian Kügler wrote: > > Reading just $PLUGINS/kf5, 52 plugins > > > > 21893.0 microsec (KServiceTypeTrader) > > 95835.0 microsec (Metadata) > > > > --> Reading metadata is 4-5 slower, ~100ms > > > >

Re: Plugin locator performance ballpark

2013-09-08 Thread David Faure
On Thursday 05 September 2013 01:04:52 Sebastian Kügler wrote: > Reading just $PLUGINS/kf5, 52 plugins > 21893.0 microsec (KServiceTypeTrader) > 95835.0 microsec (Metadata) > --> Reading metadata is 4-5 slower, ~100ms > > Reading $PLUGINS recursively, 127 plugins > 20180.0 microsec (KService