The addressbook (2.2.5) scales very poorly. I am using
the Zaurus version, and attempting to import 4000 names
and extension numbers. On the Zaurus this is only
possible if swap is enabled and loading performance is
extremely slow (minutes to launch, and import time a
good proportion of an hour).
It appears to me that the addressbook is purely memory
based and reads and writes the entire data set on
launch and closure.
Has a database paradigm been considered for storage?
(I note the Sharp DTM addressbook that comes with the
Zaurus SL-C3100 can easily handle this number of
contacts with good performance, but unfortunately has a
much poorer interface and functionality than ka/pi)
Log in to post a comment.