On Mon, Dec 5, 2011 at 7:28 AM, Carl Meyer <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/05/2011 08:10 AM, Vinay Sajip wrote: >> Not too bad for a first complete pass. Over two and a half hours to >> run, and that' s running from /dev/shm (IIUC effectively RAMdisk) and >> with fsync = off. All else set to default values. Time to investigate >> Jeremy's link to Frank Wiles' post ... > > I think first investigating any difference in performance between trunk > and your py3k branch makes more sense than heading straight to more > Postgres performance tweaks.
I agree. Carl, to be clear, if py3 pg is slower, but py2 pg is still in line w/ baseline, would that block merge to trunk? It's quite possible the problem lies in psycopg, but I think merging (with caveat emptor on the py3/pg combination) would still be good. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
