try using psycopg2 on the prod env too. pg8000 (especially the one shipped
with web2py in the latest stable, which was quite old) can exhibit memory
leaks (or, for better saying, a premature optimization resulted in an
"evil" usage of the memory for the way web2py uses pg8000).
On Friday,
On my development environment i am using psycopg2 in production pg8000, and
im not using db cache anywhere
El viernes, 14 de octubre de 2016, 10:07:43 (UTC-5), Paolo Valleri escribió:
>
> Which driver are you using for postgres? Are you using cache in models?
> Try to figure out if there are
anthony, thats a good point did not notice that, thanks
El jueves, 13 de octubre de 2016, 21:03:20 (UTC-5), Anthony escribió:
>
> That's a lot of code to review. You're probably going to have to do some
> digging and narrow it down for us. I did see one problem, though:
>
> class
Which driver are you using for postgres? Are you using cache in models?
Try to figure out if there are controllers using more memory than others.
On Friday, October 14, 2016 at 4:03:20 AM UTC+2, Anthony wrote:
>
> That's a lot of code to review. You're probably going to have to do some
>
That's a lot of code to review. You're probably going to have to do some
digging and narrow it down for us. I did see one problem, though:
class IS_BARCODE_AVAILABLE(object):
T = current.T
You can't use current in a class attribute (for the same reason it can't be
used at the top
5 matches
Mail list logo
