using the first method without cache (see below, it seems unuseful) no leaks at least in ubuntu. 30k records updated/inserted in a little less than 5 minutes. storage.db is roughly 2 GB. Memory usage is 400MB, give or take.
the second method is incorrect as posted ... maybe there are a few typos in it (and surely it doesn't replicate the first one (it just updates without inserting)) In any case for a live application those needs to be managed outside web2py. While you do those procedures the db is entirely locked, so it's a no-go if you want to do something with it in the meantime. PS: why caching is involved ? once you cache the resultset it's invalidated from the updates you're doing in it subsequently. It's just wasting ram on a not valid resultset anyway ^_^ Also, forget cache.disk, it wont' definitely be faster than SQLite. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
