Even 30-60 seconds caching might help. Browsers update their status every 30 seconds, so that would be a decent time window to offload at least some of the processing time it takes to generate the home page.
I have to agree that the home page takes far too much time to load. Something needs to be done about it, if possible. On Sep 17, 2:19 am, Bradley Sepos <[email protected]> wrote: > Here's an idea: when a client signs out of TestSwarm, take them to a > dedicated, static logout page that can be cached to infinity. > Something ala, "Thanks for running TestSwarm. You're now signed out. > _TestSwarm Home_". This would do two things: reduce load on the > server/homepage and give instant gratification to the end user. I get > a lot of timeouts when trying to load the homepage, and it kind of > sucks to click logout and have to wait; if someone wants to logout > they're probably ready to jet. > > Second thought: I'm not sure what caching you employ currently, but > the homepage would probably benefit from some sort of time-forced > caching. For instance, cache for n minutes, then get a fresh page and > cache it again. If it changes in between refreshes, who cares? A > snapshot of the currently running clients that's say, 10 minutes old, > isn't really that stale of data. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TestSwarm" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/testswarm?hl=en -~----------~----~----~----~------~----~------~--~---
