http is a STATELESS protocol. This means that for each and every request, if you want to save some data into a session, that one NEEDS to be read (eventually modified) and saved. It's not a newsflash that storing tenths of MB on the session and having it to be reparsed/saved at every request is slowing you down....and unfortunately there isn't ANY framework that will do any better
How much of a session file should you use heavily depends on the app needs: if you figure out that your "business case" needs 60 MB of a numpy array to be parsed (and so, load into memory, mangled, etc etc etc) with 50 concurrent users, you got yourself an app that needs to parse/save/manage/store/elaborate 3 GB of data... BTW, web2py pickles by default all objects saved into session. You may explore saving those files directly using npy or npz in your private/ folder .... but that's going only save you a part of the very big job you're asking your webapp to do. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
