Re: Startup performance

--===============2410249109392310565==
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/gAOm_h4M/Fck6+5Oj.2Gvu3"; protocol="application/pgp-signature"

--Sig_/gAOm_h4M/Fck6+5Oj.2Gvu3
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi!

Am 12. Okt. 2020 schrieb Robert Krawitz:

> It really is the startup that's the most visible aspect of all of this.  =
Again, that either means
> pretty fundamental changes in the storage backend, a faster XML parser, o=
r maybe a way of bringing
> up the UI while images are still loading (and since you're often going to=
 want to look at your most
> recent photos, not even very helpul).  If we stored photos in the databas=
e in _reverse_ order of
> time, though, that might be workable (I'd love to have instant access to =
my most recent basketball
> game while the rest of the file is being loaded).

Just an idea: what about "partitioning" the database. I mean we could
have a single XML file per year, per decade, per 10k images or whatever.
That way, loading the more recent images first as Robert suggested would
be easier.

Oh and BTW, thanks for all the work that has be done on KPA so far!
Really great work!

hth,
- martin

--Sig_/gAOm_h4M/Fck6+5Oj.2Gvu3
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAl+FQC4ACgkQYJf22JPx7tlQPgCfU3fPJhqPgLcUjveDY6qK7Lws
BNkAn3LRd9SQk6wNfk/Slm9sCT429Nw+
=Bza2
-----END PGP SIGNATURE-----

--Sig_/gAOm_h4M/Fck6+5Oj.2Gvu3--

--===============2410249109392310565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KPhotoAlbum mailing list
[email protected]
https://mail.kdab.com/mailman/listinfo/kphotoalbum

--===============2410249109392310565==--