Hi I never said quiet sites are not very good.
www.fishandlily.com.au is a small business we run on our property in the swan valley. We get between 40 - 60 unique visitors a day with around 200-300 pageviews a day. I think it qualifies as a very quiet site. And it isn't a startup site that will get a lot of traffic ever. We advertise locally heavily with adwords, and probably 40-50% of our customers (who visit physically) come as a result of finding us on google and going to our website. But if you visit the site most of the time its pretty quick. It went live on appengine nearly a year a go and I plan to go back to rework the caching and startup code based on my more recent work on sites like www.polytechnic.wa.edu.au (the orginal code for fishandlily.com.au hasn't been touched in all that time). So I think good use of memcache (I am not using etags yet) can make a huge difference. Regards Tim On May 20, 11:46 pm, ShriJ <[email protected]> wrote: > Not every quiet website is quiet because it is not good. It could just > mean that they are in development phase and looking to popularize it. > However, to popularize it the website needs to be shown to lot many > people. But if it is slow people won't have a good impression about > it. This would defeat the marketing effort :(. > > I'm not saying it is impossible to get over this... but it still is > one more thing to think and worry about... Oh!! Startup blues ... :-) > > Thanks for the information Tim. I'll do a rethink about the use of > memcache and look into ETags. > > -Shri > > On May 20, 12:23 am, Tim Hoffman <[email protected]> wrote: > > > > > > > Hi > > > On May 20, 3:02 pm, ShriJ <[email protected]> wrote: > > > > Yes... I see it very very often too. I just tried sending two requests > > > with a 1 minute delay between them and saw that the logs show the > > > message for both of them. This hurts performance.. :( > > > Yep, for very quiet sites. Busy sites will never really see this. > > > > Also, if the server process goes down does it also take the memcache > > > down with it. So every 30 sec not only is a new server starting but a > > > new memcache is also getting populated? > > > No that is not correct. Memcache is independant of any particular > > instance and is not cleared/loaded etc > > when an instance is started unless you are doing something in your > > apps startup code. > > > Stuff will disappear from memcache only under memory pressure (read > > full, expire times or no use for many hours) > > > By utilising memcache heavily on our sites (and not even loading the > > full stack to server pages form memcache) > > a cold start can be reduced two less than a few hundred milliseconds. > > > Google has announced they will be providing some mechanism to pay for > > a warm instance to hang around. > > Not details on it as yet. > > > I would suggest however you look at optimising your startup times, and > > using memcache aggresively (oh and also look at Etags if google's > > proxy can cache stuff for you) > > > Rgds > > > T > > > > Are there any ways of preventing this constant server going down and > > > coming up cycle? > > > > -Shri > > > > Can someone from Google confirm that there isn't anything wrong here? > > > > > T > > > > > On May 20, 11:30 am, Jaroslav Záruba <[email protected]> > > > > wrote: > > > > > > On Thu, May 20, 2010 at 5:27 AM, Tim Hoffman <[email protected]> > > > > > wrote: > > > > > > Normally you will see this on very quiet sites as instances shutdown > > > > > > if not used after a few minutes. > > > > > > Is there any official number? Because those "few minutes" sound way > > > > > optimistic to me. My experience is rather 30sec. :( > > > > > > Regards > > > > > J. Záruba > > > > > > > This is a normal log message. > > > > > > > T > > > > > > > On May 20, 10:06 am, ShriJ <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > I see that with every other request that goes to my application, > > > > > > > I get > > > > > > > the warning: > > > > > > > > "This request caused a new process to be started for your > > > > > > > application, > > > > > > > and thus caused your application code to be loaded for the first > > > > > > > time. > > > > > > > This request may thus take longer and use more CPU than a typical > > > > > > > request for your application." > > > > > > > > I presume a new process implies a new process of dev_appserver. > > > > > > > > Why does this happen? Is there any documentation about when a new > > > > > > > process start? Is there any way to get over this? > > > > > > > > Thanks in advance. > > > > > > > -Shri > > > > > > > > -- > > > > > > > You received this message because you are subscribed to the > > > > > > > Google Groups > > > > > > "Google App Engine" group. > > > > > > > To post to this group, send email to > > > > > > > [email protected]. > > > > > > > To unsubscribe from this group, send email to > > > > > > [email protected]<google-appengine%2Bunsubscrib > > > > > > [email protected]> > > > > > > . > > > > > > > For more options, visit this group athttp:// > > > > > > groups.google.com/group/google-appengine?hl=en. > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > > Groups > > > > > > "Google App Engine" group. > > > > > > To post to this group, send email to > > > > > > [email protected]. > > > > > > To unsubscribe from this group, send email to > > > > > > [email protected]<google-appengine%2Bunsubscrib > > > > > > [email protected]> > > > > > > . > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/google-appengine?hl=en. > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "Google App Engine" 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 > > > > > athttp://groups.google.com/group/google-appengine?hl=en. > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Google App Engine" 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 > > > > athttp://groups.google.com/group/google-appengine?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google App Engine" 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 > > > athttp://groups.google.com/group/google-appengine?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" 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 > > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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 > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
