KIO directory listing - CPU slows down SSD

[Mark Gaiser]

On Mon, Jun 2, 2014 at 11:47 PM, Frank Reininghaus
<frank78ac at googlemail.com> wrote:
> Hi,
>
> 2014-06-02 23:39 GMT+02:00 Frank Reininghaus:
>> Hi,
>>
>> 2014-06-02 20:54 GMT+02:00 Mark Gaiser:
>>> On Mon, Jun 2, 2014 at 6:42 PM, Aaron J. Seigo wrote:
>>>> On Thursday, May 29, 2014 16:32:28 Mark Gaiser wrote:
>>>>> dolphin on a massive folder. In fact, those that use kio::listdir for
>>>>> listing folders only have interfaces that become usable when all
>>>>> entries are fetched.
>>>>
>>>> assuming these UIs receive maintenance over the next years, this pattern is
>>>> likely to fade away. instant feedback and incremental listing is a current
>>>> reality.
>>>>
>>>> you know what would be very nice (but rather complex to achieve...)? for the
>>>> client side of a KIO listing to say "i only want the first N items anyways,
>>>> i'll let you know when i can handle more..." and for sorting to be optionally
>>>> done on the slave side.
>>>
>>> That would be very nice since you would cut IPC communication
>>> massively (depending on the folder) to just those that you see which
>>> would result in even insanely large folders to be presented to the
>>> user near instantly.
>>>
>>> But don't you just move logic to the slave that way? And lose
>>> flexibility in the apps using the slave (like dolphin? Oh and
>>> complicating kio "a bit" to pass a sorting and/or grouping style.
>>> Right now it's not really difficult to add a completely new sort order
>>> in dolphin, but that becomes very difficult when you want to let the
>>> slave do the sorting.
>>
>> Yes, such an approach would indeed require additional complexity in
>> KIO and the slaves and would sacrifice flexibility.
>>
>> Therefore, it might be questionable if this is really the way to go -
>> I didn't really mean that this should be implemented when I said that
>> I had also thought about this approach in my reply to Aaron.
>> Sometimes, I just dream and think about things that we could do if we
>> had infinite resources ;-)
>
> As a side note, if we had infinite resources, making Dolphin QML-based
> would also have a high priority for me, but since my resources are
> quite limited, I will probably not be able to take part in any such
> effort in the near future.

I have high hopes that the feature difference between dolphin and
accretion will close in the coming.. years.. at which point we can
just drop dolphin and use accretion ^_-