KMountPoint::probablySlow and cifs mount points

Albert Astals Cid aacid at kde.org
Sun Nov 24 16:05:11 GMT 2013


In Okular we just got bug 
https://bugs.kde.org/show_bug.cgi?id=327846
PDF Render time is unreasonably slow over cifs on high latency (WAN) network 
connections

Basically the issue is that poppler is quite read-intensive over files, 
reading them over and over, and since the file is "local but really remote" it 
takes ages to render for big files.

The only solution i can think of is doing a local copy and then working on 
that.

I saw KMountPoint::probablySlow that says

    /**
     * Checks if the filesystem that is probably slow (nfs mounts).
     * @return true if the filesystem is probably slow
     */

And then returns true if the the filesystem type of the mount is nfs, autofs 
or subfs.

Any objection to replacing

    /**
     * Checks if the filesystem that is probably slow (nfs mounts).
     * @return true if the filesystem is probably slow
     */

to

    /**
     * Checks if the filesystem that is probably slow (network mounts).
     * @return true if the filesystem is probably slow
     */

and adding cifs to the list of mounttypes that are "probablySlow"?

Or anyone has a better suggestion to fix this issue?

Cheers,
  Albert




More information about the kde-core-devel mailing list