[PonyORM-list] Controlling session caching

[Alexander Kozlovsky]

Hi Matthew!

At first sight it looks like a memory leak. Also it is possible that bigger
values of x in your loop retrieve larger number of objects and hence
require more memory?

Regarding memory leak: after db_session is over, Pony releases pointer to
session cache, and in the best case all cache content will be gathered by
garbage collector. But if your code still holds a pointer to some object in
the cache, that will prevent garbage collection, because objects inside a
cache are interconnected. Are you holding some pointers to objects from
previous db sessions?

It is possible that we have some memory leak inside Pony, but right now we
are not aware of it.

You mentioned in one of your previous messages that in your code you
perform cascade deletion of multiple objects, which all are loaded into
memory. Does you current program perform something like that?

In principle, I'm for pruning cache more aggressively on db_session exit,
but unfortunately some people like to continue working with objects after
exiting from db_session (for example, generate HTML content using some
template engine, etc.), although in my opinion it is more correct to
perform such actions inside db_session.


Regards,
Alexander


On Thu, Apr 14, 2016 at 10:46 PM, Matthew Bell <matthewrobertbell at gmail.com>
wrote:

> Hi,
>
> I have code like:
>
> for x in list_of_ints:
>   with db_session:
>      # do lots of database processing tied to x
>
> I am doing it like this to stop the pony cache from using a lot of memory,
> but cache usage still grows over time. How can I stop this happening?
>
> Thanks,
>
> Matt
>
> --
> Regards,
>
> Matthew Bell
>
> _______________________________________________
> ponyorm-list mailing list
> ponyorm-list at ponyorm.com
> /ponyorm-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ponyorm-list/attachments/20160415/78aa0722/attachment.html>