On Sun, Jun 5, 2011 at 11:45 AM, Thiago Macieira <thi...@kde.org> wrote: > Em Sunday, 5 de June de 2011, às 14:38:07, tushar mehta escreveu: >> But the problem is that even if KIO is filling up the kernel buffer at some >> rate >> but the application is not reading that data at same rate. Then situation >> will remain same. >> >> Just a thought, it can be wrong also. > > It is wrong. > > The chain is as fast as the slowest link. So if the ioslave is reading at 60 > kB/s from the network and writing that much into the kernel buffer, but the > application is only reading at 4 kB/s, the kernel buffer will grow in size. It > will grow until that buffer reaches its limit, at which point the ioslave will > no longer be able to write. It will block until the application reads a chunk > of data. > > After that point in time, the ioslave's rate will be limited by the > application's read rate.
How big is the kernel buffer, on average? Is the connection done on a per-file or per-transfer basis? (i.e. if you copy and paste 20 files in dolphin, is that one connection or 20?) If this is a per-file thing, and it is in the hundreds of kilobytes to a few megabytes, the buffer may never fill. -Todd >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
