On Aug 1, 2014, at 10:56 AM, Jim Lawson wrote:
The session data stored for this webapp is … large. We’ve moved it
out of the database and onto the local filesystem, which has helped the
database a lot, but now we’re just filling the local disk (and probably
thrashing I/O besides)Currently there are 3126 session data files in /tmp/glcp. 46 of them
are over 100MB in size! A gross way we could handle this is a cron job
that runs (say once an hour):find /tmp/glcp -type f -size +5M -exec rm -f {} ;
Really, this app should not store so much data in the session! But you
asked for “what SAA can do about this”.Any other suggestions?
I’ve been mulling this over for a week now and getting nowhere. Perform a search -> store results ‘set’ in session -> read from session to display results -> retain last MAX_SETS Results is the central,design philosophy of the application ( as designed by long gone CS grad student). Search for trees, get 2000+ results! what should we do with them?
The related problem: start_session when session > 100mb results in php out of memory error. Can we crank this up, too?
Couple of things I’ll try: change max_sets from current 7 to 2 or 3. Remove browse all 75000 images option, too unwieldy. Expire sessions more freqently.
Clearly this app does not scale well. Good mews is much code assumes a 5 digit ID number, so we are limited to 99999 images.
