On 27 févr. 06, at 09:19, Mark Edwards wrote:
On Feb 26, 2006, at 11:56 PM, Leonard Bouchet wrote:
Hum, that's a good question I can't find an answer for the moment. To
be sure we correctly identified the problem, could you simply replace
the rcube_imap.inc::message_index function with the one below (around
line 643)? This one only issues a sort command without checking the
cache at all. If the problem persists when you see a new message
(with the list sorted by something else than date_DESC), that's
effectively strange, because it does a lot less than the
_list_headers function, so should be significantly faster, or at
least equal.
It was very fast (and of course the prev/next email links didn't work)
so it was the behavior you expected.
Actually, the prev/next links should continue working normally (and
they do on my system). Did you replace the function within the
*previously patched* code?
Significantly faster, yes, given that otherwise clicking on a message
in a large sorted box is so slow it doesn't complete. With the
simplified function, it took like 1.5 seconds.
I still can't understand why this gives different results, but I'm not
hopeless.
c3 SORT (SUBJECT) US-ASCII ALL
# how much time does it take to get the answer?
c3 OK Completed (12592 msgs in 0.633 secs)
c4 UID SORT (SUBJECT) US-ASCII ALL
# how much time does it take to get the answer?
c4 OK Completed (12592 msgs in 0.633 secs)
Its fast.
Good, so we can focus on the real problems, now.
-l
