Yes, I would say cache.ram might be a better approach. Also, keep in mind that although you might want to check every second or two, you don't have to update the progress variable after every single record insertion. For example, for a precision of 1%, just update the progress after every 300 insertions.
Anthony On Wednesday, February 17, 2016 at 10:06:33 AM UTC-5, Alfonso Serra wrote: > > >> Perhaps you should update a field in some db table and use it instead of >> session. >> > > Please note that the end of this, is to create an ajax progress bar that > indicates the numbers of records being inserted on a request. > > Although that might work as well, still it isnt good to read and write a > record each second (progress update interval) when im performing the > insertion of 30k records. > > The optimal way to solve this is, as your company name indicates, is > persistent memory, so the session was my first choice until Anthony said > that it has to be written to disk. And either writing to disk or db isnt > good. > > web2py Scheduler is a candidate to solve a problem like this but im not > sure yet. > Check the progress of a background job, might do the trick or caching a > variable in ram (althought the variable has to be updated frequently) or > even a temporary memory table in the db. > > Thanks. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
