[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: low performance of kio
From:       mosfet <mosfet () mandrakesoft ! com>
Date:       2000-04-20 18:18:22
[Download RAW message or body]

Ian Zepp wrote:
> 
> On Thu, Apr 20, 2000 at 10:11:57AM +0200, Stephan Kulow wrote:
> > Stefan Schimanski wrote:
> > >
> > > Am Wed, 19 Apr 2000 schrieb Stephan Kulow:
> > > > Stefan Schimanski wrote:
> > > > >
> > > > > Hi,
> > > > > I did some performance test of the KIO library and was very disappointed. A
> > > > > SimpleJob reading a local file only transfered 180-200 KB/s. Reading with stdio
> > > > > functions (fopen, fread, etc.) transfer more than 3000 KB/s! Although KIO works
> > > > > in background with signals and slots it should be faster I think. Is there any
> > > > > chance to speed it up?
> > > > >
> > > > Why should it be faster? KIO isn't really made for reading local files,
> > > > but
> > > > for network transparency, where 200KB/s is most often good enough. if
> > > > you want
> > > > to read a local file, use fopen and fread. What you do when using kio is
> > > > doing
> > > > the same, but redirect the commands and the data to another process,
> > > > inheritly
> > > > making it slower as the IPC bandwidth is far lower than the usual file
> > > > reading.
> > >
> > > I agree. But why are local jobs done in the process at all. Wouldn't it be much
> > > better to do them in a in process file? Only an idea...
> >
> > Because that blocks the application. If you want speed, use fread - if
> > you want
> > nonblocking IO, use KIO
> >
> 
> Forgive me if this sound naive, but I was under the impression that KIO should be used
> whenever possible, in order to promote said "transparency". If you insist that ppl
> use which ever method is more appropriate, then use fread for local files and nfs or
> ftp for network operations, and skip KIO altogether.
> 

This is kindof what I was thinking but I was too much a newbie with KIO
to mention it ;-) I thought one of the main advantages of KIO was to be
able to use the same chunk of code for both local and remote files >:)
I'm totally ignorant here but perhaps it would be good to add hacks to
KIO that optionally just use normal I/O without slaves for local files
but generate the same signals as other jobs (reading/writing a chunk of
data then generating a signal)? Dunno if this is possible or not. It's
certainly not good to be saying "Don't use KIO for local file access".

> Regards
> 
> Ian
> 
> >

-- 
Daniel M. Duley - Unix developer & sys admin.
http://www.mosfet.org - The place for KDE development news.
mosfet@mandrakesoft.com
mosfet@kde.org

[prev in list] [next in list] [prev in thread] [next in thread]