https://bugs.kde.org/show_bug.cgi?id=478457
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sit...@kde.org
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
> no high CPU/IOwait/Network from kioslave5 (media previews still working)
You may need to explain this expectation in greater detail. How do you
reconcile remote-IO-without-wait-time with having to access remote data, as
would be the case during preview generation? At face value there's always an
unknown amount of wait time, because we don't know network throughput and
latency, and then remote drive throughput and latency. Or put simply: the only
way not to wait is to not read data; when reading data we need to wait for the
IO.
> A naive analysis would seem to suggest there are less invasive and resource
> intensive ways to generate media previews
Such as?
--
You are receiving this mail because:
You are watching all bug changes.
