Hi Malcolm,

I don't have a sufficiently large code base to test this with but I would be surprised if turning on AutoCommit didn't significantly impact the performance of indexing. My thinking on this was that as part of Feature Request 1691378 (Rearchitect the DB backends) that the LXR::Index::DBI class would define an abstract "TransactionCompleted()" subroutine that derived classes (such as LXR::Index::Postgres) could implement to call commit or not as they choose.


> From: malcolm.box@gmail.com
> Date: Wed, 6 May 2009 22:22:46 +0100
> To: lxr-developer@lists.sourceforge.net; lxr-general@lists.sourceforge.net
> Subject: [Lxr-general] Large installations running on Postgres?
> Hi,
> I'm wondering what the performance (dis)advantage is of having
> DBI::AutoCommit switched off for Postgresql. As part of a general
> tidy-up of the Index classes I'm considering switching AutoCommit to
> on - but I don't have a decent-sized install to check the performance
> impact.
> Has anyone got a large-ish installation running using Postgres who
> could measure the performance with AutoCommit switched on and off -
> the relevant line to change is line 43 in lib/LXR/Index/Postgres.pm.
> Any data would be much appreciated!
> Cheers,
> Malcolm
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Lxr-general mailing list
> Lxr-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxr-general

Share your photos with Windows Live Photos Free. Try it Now!