On Thu, Oct 3, 2013 at 9:42 AM, Theodore Ts'o <[email protected]> wrote: > On Tue, Oct 01, 2013 at 12:34:38PM -0500, Felipe Contreras wrote: >> Pushing the updates is not the problem for me, as it's usually a >> couple of messages that get updated, it's fetching them. Even if >> nothing changed at all, it takes a long time. > > What's your ping round trip time (RTT) to your IMAP server?
Seems to be around 50ms. Sometimes it spikes up, but that's probably the wireless driver acting up. > I didn't do this for the message fetching part of the protocol, > because wrapping the state to allow multiple fetches to be done in > parallel and asynchronously was a lot more difficult, and since the > time to download the a larger message versus the overhead caused by > the lock-step protocol made this not as much of a huge win. > > Now, the cruise ship network had a very low bandwidth as well as a > high latency time, so that's why the tradeoff was such that it wasn't > worth my effort to try to optimize the message fetch processing in > mbsync. If you have a network connection which has a higher > bandwidth, but a much longer RTT time --- say, if you were an > astronaut on a Marse mission trying to use mbsync, then it would > definitely make sense to fetch multiple messages in parallel. Yeah, but I don't think there's much of a need for that. The problem is not how fast the messages are downloaded, but how to define and limit the messages that should be downloaded. -- Felipe Contreras ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
