Issue is kind of resolved.
I created a dummy.. small sqlite file
and read that sqlite the same way as large ones are done.
and then do
for row in some_rows.exclude(lambda row: row.id > 0)
again.
This tends to free up memory.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Document
you still have alert_rows in memory.
it would be
for row in alert_rows.exclude ...
pass
del alert_rows
gc.collect()
On Friday, 12 February 2016 05:45:49 UTC, Jitun John wrote:
>
> I am using to remove rows...
>
> for row in alerts_rows.exclude(lambda row: row.id > 0):
> pass
>
>
> On Frida
I am using to remove rows...
for row in alerts_rows.exclude(lambda row: row.id > 0):
pass
On Friday, February 12, 2016 at 5:49:38 AM UTC+5:30, Alfonso Serra wrote:
>
> You can try "del rows" to remove the reference from memory before
> collecting
> del a single row raises a TypeError but d
You can try "del rows" to remove the reference from memory before
collecting
del a single row raises a TypeError but del rows doesnt. It may help.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com
I believe it is caching everything to memory.
Here is the code I have.
But yes, not a web2py issue.
def read_manager_rows():
manager_db_conn = DAL('sqlite://manager.sqlite', folder=get_current_path(),
auto_import=True)
global manager_rows
manager_rows = manager_db_conn(manager_db_conn
This is not a web2py specific problem. Are you caching something is ram? Do
you use a library that may be creating circular references?
On Friday, 5 February 2016 01:56:39 UTC-6, Jitun John wrote:
>
> My application, basically parses log files and presents that using web2py
>
> So each flat file
6 matches
Mail list logo
