Thanks for your response. PostGreSql access via web2py is remains very slow at this point.
Adding for instance a record takes 30-60 seconds. Everything that accesses the DB seems to have 30 second overhead. * Hardware : duo-core 2gz, 32MB cache hard drive, 1gig Ram. * Via Python having tested postgre access in same environment, issuing select (python and psycopg 2) it is instant as one would expect on both large and small tables. * I've converted the Cookbook application to access Postgre so can use that as a test example. Any tips on where to look in solving this web2py postgre slow performance appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
