Den 09. april 2014 16:51, skrev Patrick Ohly:
Performance and storage are important but I don't think they are what
limits this today. I think it is usability. Particularly in terms of
undoing individual changes (even of individual fields within a single
object).
I remember that Ove turned off "dumpData" for Maemo because it was slow.
But perhaps my memory fails me here.
Well, I don't turn dumpData off by default. The Maemo frontend turns off
printChanges by default, but leaves dumpData enabled.
However, dumpData *is* horribly slow. Easily 10 times slower than the
sync itself, probably more. Many users with large PIM databases have
been forced to turn it off to get tolerable performance and stability.
For example, the N900 has a watchdog timer that auto-reboots the phone
if the OS becomes unresponsive for too long. Heavy I/O on the phone's
internal storage can in some cases cause this (especially if all that
I/O causes OS processes to get swapped out, due to the N900's undersized
RAM).
On the N9, a lot of PIM data have to be transferred over D-Bus, which
makes dumpData quite slow, sometimes causing timeout issues.
On the Jolla, during a slow backup, the OS might decide that nothing is
going on and power down the CPU. Then the remote peer would probably
time out. (Although I think I know how to fix that, I haven't had time
to do it yet.)
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
