On Dec 5, 5:28 pm, Carl Meyer <[email protected]> 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.
For me the tests do not feel any slower on Python3 than they do on Python2. Taking a few assorted tests, other is Python2 and trunk HEAD, other Python3 and py3k branch HEAD: python3 ./runtests.py --settings=test_pgsql admin_views queries transactions Ran 362 tests in 175.297s FAILED (errors=5, skipped=3, expected failures=1) ./runtests.py --settings=test_pgsql admin_views queries transactions Ran 362 tests in 209.128s OK (skipped=4, expected failures=1) As can be seen, there is no reason to expect python3 to be slower. It is actually faster in this little test is, but that is probably because my machine happens to generate wildly varying benchmark results (powersaving or something doing weird things behind the scenes). - Anssi -- 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.
