[google-appengine] Re: Hosting static files on GAE and using own domain.

[Raghu Kiran]

Small changes to the URL's below.

Blog link :  
http://blog.recurtrix.com/2012/08/free-hosting-for-your-web-applications.html
 

Google App link: http://www.recurtrix.com

On Saturday, 18 August 2012 18:05:52 UTC+5:30, Raghu Kiran wrote:
>
> Hi Omne,
>
> Please find my answers to your questions below.
>
> Do you I have to do anything special for hosting static HTML pages? 
> >>Nope, its far more easier, simpler and less resource consuming than 
> servlets and JSP's.
>
> I read on the internet that with Python we should configure a file for 
> static files, what about Eclipse? 
> >>Yes, python does. I wrote a blog on how to do this in eclipse, the link 
> is still under construction, I tried to make the stuff in it as simple as 
> possible. Let me know in case you need any support.
>
> http://blog.recurtrix.com/2012/08/host-your-static-website-in-google-for.html
>  
>
> I'm going to remove all unwanted files from project folders and add my 
> website files and folders to the project and then deploy it. is this what 
> should do? 
> >>Yes, Thats what you have to do the blog link above should guide you 
> with the process in detail.
>
> If I want to point my own domain to my project, should I do it before 
> uploading the project or after it? because I noticed GAE has its own domain 
> (appspot.com) what if I don't want that my website be available at this 
> address too? 
> >>You can point to your own domain. http://www.recutrix.com is one such 
> hosted app. 
> >>You can point it to your own domain after hosting your app.
> >> for the last part, I do not have a answer, please post another question 
> for it.
>
> Best regards,
> Raghu
>
> On Wednesday, 15 August 2012 12:24:15 UTC+5:30, Omne wrote:
>>
>> Hi, I'm trying to host my website on GAE, it's just a few  HTML page and 
>> images. I downloaded the Eclipse and all its required plugins and GAE SDK, 
>> I think I were able to upload (deploy) a project successfully, now I can 
>> see an index page on myapp.appspot.com wiich says "Hello App Engine!".
>>
>> Now I have a few questions:
>> Do you I have to do anything special for hosting static HTML pages?
>> I read on the internet that with Python we should configure a file for 
>> static files, what about Eclipse?
>> I'm going to remove all unwanted files from project folders and add my 
>> website files and folders to the project and then deploy it. is this what 
>> should do?
>> If I want to point my own domain to my project, should I do it before 
>> uploading the project or after it? because I noticed GAE has its own domain 
>> (appspot.com) what if I don't want that my website be available at this 
>> address too?
>>
>> Thank you for your help.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/oNEdPNjiiTIJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Hosting static files on GAE and using own domain.

[Raghu Kiran]

Small changes to the URL's below.

Blog link :  
http://blog.recurtrix.com/2012/08/free-hosting-for-your-web-applications.html
 

Google App link: http://www.recurtrix.com


On Wednesday, 15 August 2012 12:24:15 UTC+5:30, Omne wrote:
>
> Hi, I'm trying to host my website on GAE, it's just a few  HTML page and 
> images. I downloaded the Eclipse and all its required plugins and GAE SDK, 
> I think I were able to upload (deploy) a project successfully, now I can 
> see an index page on myapp.appspot.com wiich says "Hello App Engine!".
>
> Now I have a few questions:
> Do you I have to do anything special for hosting static HTML pages?
> I read on the internet that with Python we should configure a file for 
> static files, what about Eclipse?
> I'm going to remove all unwanted files from project folders and add my 
> website files and folders to the project and then deploy it. is this what 
> should do?
> If I want to point my own domain to my project, should I do it before 
> uploading the project or after it? because I noticed GAE has its own domain 
> (appspot.com) what if I don't want that my website be available at this 
> address too?
>
> Thank you for your help.
>

On Wednesday, 15 August 2012 12:24:15 UTC+5:30, Omne wrote:
>
> Hi, I'm trying to host my website on GAE, it's just a few  HTML page and 
> images. I downloaded the Eclipse and all its required plugins and GAE SDK, 
> I think I were able to upload (deploy) a project successfully, now I can 
> see an index page on myapp.appspot.com wiich says "Hello App Engine!".
>
> Now I have a few questions:
> Do you I have to do anything special for hosting static HTML pages?
> I read on the internet that with Python we should configure a file for 
> static files, what about Eclipse?
> I'm going to remove all unwanted files from project folders and add my 
> website files and folders to the project and then deploy it. is this what 
> should do?
> If I want to point my own domain to my project, should I do it before 
> uploading the project or after it? because I noticed GAE has its own domain 
> (appspot.com) what if I don't want that my website be available at this 
> address too?
>
> Thank you for your help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/R5e8IxoSab8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[Jeff Schnitzer]

On Sat, Aug 18, 2012 at 8:59 PM, pphalen  wrote:
>> Apps with a lot of rapidly mutating aggregation are hard.
>
> Hi, I'm new to app engine, so this is news to me. Could you please
> characterize a bit more? E.g., what is "a lot"?

Nothing in the datastore can change faster than once per second;
imagine trying to keep a count of products sold when you're selling
hundreds per second.  Sharding helps but it becomes tricky to get the
value in a timely manner when you get to hundreds of shards.  If you
need a transactionally accurate count (say, you are selling N units
and you must not sell N+1 units) this becomes even harder - you have
to go out of the datastore to another tool like memcache increment().

There are other data storage technologies that are optimized for rapid
updates to atomic data.  Redis, Mongo, and of course traditional
RDBMSes solve this problem pretty easily for most typical scaling
needs.  There isn't an equivalent tool in the GAE toolbox.  This
doesn't mean you can't use GAE even if your app does some of this
aggregation... but if you do a lot of it, the platform works against
you rather than for you.

Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Asking for your help: How do you develop apps today and in the future?

[Wolfgang Gruener]

We recently launched our web app survey to gain more insight in current web app 
and app development trends. We would be excited if you guys could take 5 
minutes and head over to the form and fill out a fee questions. As our thank 
you, please leave your email address at the end of the survey and we will send 
you a complimentary copy of the resulting whitepaper with the results of the 
survey, which will give you an overview of web application development trends 
happening right now and what technologies are important to other developers, 
which will hopefully assist you in your ongoing developer efforts. Thank you 
for your participation! -Wolfgang

You can find the survey here:
https://docs.google.com/spreadsheet/viewform?formkey=dFBWTS14cUR1QlNXQVpGbXMyMk50TWc6MQ#gid=0

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/wY1USKKK_jkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[pphalen]

> Apps with a lot of rapidly mutating aggregation are hard.

Hi, I'm new to app engine, so this is news to me. Could you please 
characterize a bit more? E.g., what is "a lot"?

On Saturday, August 18, 2012 1:19:51 PM UTC-7, Jeff Schnitzer wrote:
>
> On Sat, Aug 18, 2012 at 2:21 PM, Mos > 
> wrote: 
> > 
> > I'm surprised that you are still go with GAE for new applications? 
> > You had your own "experiences" from what I saw on this list. ;) 
> > 
> > I'm not recommending GAE anymore. I tell my customer to go with other 
> > platforms. After one year following discussions and issues I don't thing 
> > reliability will be improved on GAE in near future (at least for small 
> > and mid-size applications). 
>
> I will confess that my enthusiasm for GAE has tempered somewhat, but 
> every platform has issues.  All my GAE apps have parts that run in 
> other cloud providers where it makes sense.  That doesn't bother me. 
>
> The shining gem in GAE-land is the datastore.  It would be 
> extraordinarily hard to reproduce a distributed, replicated, 
> fault-tolerant, infinitely-scaling, self-managing database.  Maybe 
> Amazon's DynamoDB is getting close - I certainly like the performance 
> of it, but it still seems to lack a lot of the features of the GAE 
> datastore.  All other data storage solutions I am familiar with 
> require a significant amount of maintenance as they scale, and I don't 
> want to think about that.  I have no ops team and don't ever want one. 
>
> The task queue and memcache work well and are nicely integrated. I 
> like that you can transactionally add a task.  But yeah, these parts 
> can be replicated elsewhere. 
>
> My main points of frustration are: 
>
>  * Requests that go to cold start instances.  I think this will 
> eventually get fixed. 
>
>  * $100/mo SSL.  Way too hard on startups, and pushes people away from 
> the mantra that everything should be ssl all the time. 
>
>  * General performance.  Some things are just slower than they should 
> be.  For example, we (Voost) proxy OSM map tiles because Mapquest 
> doesn't support HTTPS - everything must be HTTPS or browsers show 
> mixed content warnings.  Proxying through GAE was visibly slow, and 
> requests would often fail even with multiple retries.  It's possible 
> that this is because Akamai (which serves the tiles) is throttling 
> requests from GAE urlfetch; dunno.  But moving our https tile proxy to 
> nginx on Heroku made a _world_ of difference.  It's like night and 
> day. 
>
>  * GAE is actually pretty expensive, in a way that isn't so obvious 
> from the price chart.  The natural tendency is to compare an 
> "instance" of GAE to an "instance" from some other service, and by 
> this standard GAE is fairly expensive.  But each GAE instance can 
> handle a lot less load than an "instance" from almost any other 
> service, so there is another multiple you wouldn't necessarily expect. 
>  For most apps the added expense is still tolerable, but for some apps 
> (ie Richard's game) it's downright pathological. 
>
> There are a number of other tricks and difficulties on GAE but there 
> are almost always workarounds.  It's the nature of working on a large, 
> clustered, distributed system that some things (eg, aggregating 
> rapidly changing data) are hard.  Overall I still recommend GAE for 
> most standard webappy kinds of things... but there are some apps I 
> would steer away: 
>
>  * Apps with a lot of transactional logic are hard. 
>  * Apps with a lot of ad-hoc query needs are hard. 
>  * Apps with a lot of rapidly mutating aggregation are hard. 
>
> Someday when I have more time I might write a short "GAE Survival 
> Guide" and sell it for a few bucks as an ebook. 
>
> Jeff 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/qIBLiyr_n-sJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] python27 helloworld application doesn't work when application id is changed

[Robert Fischer]

Changing the appid in the app.yaml should work fine to upload the app.

You can also use appcfg.py --application=... to override the "application:"
line specified in the app.yaml. More info here:
https://developers.google.com/appengine/docs/python/tools/uploadinganapp

-Robert

On Sat, Aug 18, 2012 at 12:48 PM, dt_da wrote:

> Hello,
>
> I downloaded the app sdk and went through the helloworld example for
> python27, everything worked fine until the very last bit of the tutorial
> which was about deploying the application. I created a new application id
> on google, which was different to the name helloworld. The tutorial asked
> me to change the application property in the app.yaml to the application id
> - which is what I did and it came up with a error both on the SDK version
> and deployed version.
>
> How do I deploy an application with a application id different to the name
> is was initially created in the app.yaml file?? I can't find anything on
> tutorial about this?
>
> --
> *Din Tech notice*
> Please inform us if this message has gone astray - before deleting it - by
> forwarding this email to postmas...@dintechnology.com w**ith RETURN as
> the subject-line.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/-oYKV0W3q5cJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] python27 helloworld application doesn't work when application id is changed

[dt_da]

Hello,

I downloaded the app sdk and went through the helloworld example for 
python27, everything worked fine until the very last bit of the tutorial 
which was about deploying the application. I created a new application id 
on google, which was different to the name helloworld. The tutorial asked 
me to change the application property in the app.yaml to the application id 
- which is what I did and it came up with a error both on the SDK version 
and deployed version.

How do I deploy an application with a application id different to the name 
is was initially created in the app.yaml file?? I can't find anything on 
tutorial about this?

-- 

--
*Din Tech notice*
Please inform us if this message has gone astray - before deleting it - by 
forwarding this email to postmas...@dintechnology.com with RETURN as the 
subject-line.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/-oYKV0W3q5cJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] 500 Server Error

[Gowtham Gutha]

On Friday, 20 April 2012 21:26:48 UTC+5:30, Robert Kluin wrote:
>
> Hey Gowtham,
>   You need to take a look at your apps logs and see what the exception
> is being thrown.
>
>
> Robert
>
> On Thu, Apr 19, 2012 at 05:24, Gowtham Gutha 
> > 
> wrote:
> > I tried a sample java servlet application and deployed it to Google App
> > Engine through Eclipse. My sample project worked well on my localhost 
> but on
> > appengine it did not.
> >
> > http://guthagowtham.appspot.com/ is my project url. This is simple test 
> it
> > takes input from the user and prints it on the other page.
> >
> > When i typed something and clicked on submit, it is unable to display the
> > output. Here is what i got
> > http://guthagowtham.appspot.com/simple?name=sample&submit=submit
> >
> > The following message is displayed
> >
> > Error: Server Error
> >
> > The server encountered an error and could not complete your request.
> >
> > If the problem persists, please report your problem and mention this 
> error
> > message and the query that caused it.
> >
> > Is there any solution for this.
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msg/google-appengine/-/YDMQyt2P0goJ.
> > To post to this group, send email to 
> > google-a...@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
>


Here is the log

Uncaught exception from servlet
java.lang.UnsupportedClassVersionError: com/simple/SimpleServlet : Unsupported 
major.minor version 51.0
at 
com.google.appengine.runtime.Request.process-78c19a91859a55eb(Request.java)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
at org.mortbay.util.Loader.loadClass(Loader.java:91)
at org.mortbay.util.Loader.loadClass(Loader.java:71)
at org.mortbay.jetty.servlet.Holder.doStart(Holder.java:73)
at 
org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:242)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at 
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at 
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at 
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at java.lang.Thread.run(Thread.java:679)

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/RsFKfWtW5V4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[Mos]

> Someday when I have more time I might write a short "GAE Survival
> Guide" and sell it for a few bucks as an ebook.

That's seems to be a good motivation to invest so much time in GAE
issues. ;)  I would had bought the book one year ago

On Sat, Aug 18, 2012 at 10:19 PM, Jeff Schnitzer  wrote:
> On Sat, Aug 18, 2012 at 2:21 PM, Mos  wrote:
>>
>> I'm surprised that you are still go with GAE for new applications?
>> You had your own "experiences" from what I saw on this list. ;)
>>
>> I'm not recommending GAE anymore. I tell my customer to go with other
>> platforms. After one year following discussions and issues I don't thing
>> reliability will be improved on GAE in near future (at least for small
>> and mid-size applications).
>
> I will confess that my enthusiasm for GAE has tempered somewhat, but
> every platform has issues.  All my GAE apps have parts that run in
> other cloud providers where it makes sense.  That doesn't bother me.
>
> The shining gem in GAE-land is the datastore.  It would be
> extraordinarily hard to reproduce a distributed, replicated,
> fault-tolerant, infinitely-scaling, self-managing database.  Maybe
> Amazon's DynamoDB is getting close - I certainly like the performance
> of it, but it still seems to lack a lot of the features of the GAE
> datastore.  All other data storage solutions I am familiar with
> require a significant amount of maintenance as they scale, and I don't
> want to think about that.  I have no ops team and don't ever want one.
>
> The task queue and memcache work well and are nicely integrated. I
> like that you can transactionally add a task.  But yeah, these parts
> can be replicated elsewhere.
>
> My main points of frustration are:
>
>  * Requests that go to cold start instances.  I think this will
> eventually get fixed.
>
>  * $100/mo SSL.  Way too hard on startups, and pushes people away from
> the mantra that everything should be ssl all the time.
>
>  * General performance.  Some things are just slower than they should
> be.  For example, we (Voost) proxy OSM map tiles because Mapquest
> doesn't support HTTPS - everything must be HTTPS or browsers show
> mixed content warnings.  Proxying through GAE was visibly slow, and
> requests would often fail even with multiple retries.  It's possible
> that this is because Akamai (which serves the tiles) is throttling
> requests from GAE urlfetch; dunno.  But moving our https tile proxy to
> nginx on Heroku made a _world_ of difference.  It's like night and
> day.
>
>  * GAE is actually pretty expensive, in a way that isn't so obvious
> from the price chart.  The natural tendency is to compare an
> "instance" of GAE to an "instance" from some other service, and by
> this standard GAE is fairly expensive.  But each GAE instance can
> handle a lot less load than an "instance" from almost any other
> service, so there is another multiple you wouldn't necessarily expect.
>  For most apps the added expense is still tolerable, but for some apps
> (ie Richard's game) it's downright pathological.
>
> There are a number of other tricks and difficulties on GAE but there
> are almost always workarounds.  It's the nature of working on a large,
> clustered, distributed system that some things (eg, aggregating
> rapidly changing data) are hard.  Overall I still recommend GAE for
> most standard webappy kinds of things... but there are some apps I
> would steer away:
>
>  * Apps with a lot of transactional logic are hard.
>  * Apps with a lot of ad-hoc query needs are hard.
>  * Apps with a lot of rapidly mutating aggregation are hard.
>
> Someday when I have more time I might write a short "GAE Survival
> Guide" and sell it for a few bucks as an ebook.
>
> Jeff
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[Jeff Schnitzer]

On Sat, Aug 18, 2012 at 2:21 PM, Mos  wrote:
>
> I'm surprised that you are still go with GAE for new applications?
> You had your own "experiences" from what I saw on this list. ;)
>
> I'm not recommending GAE anymore. I tell my customer to go with other
> platforms. After one year following discussions and issues I don't thing
> reliability will be improved on GAE in near future (at least for small
> and mid-size applications).

I will confess that my enthusiasm for GAE has tempered somewhat, but
every platform has issues.  All my GAE apps have parts that run in
other cloud providers where it makes sense.  That doesn't bother me.

The shining gem in GAE-land is the datastore.  It would be
extraordinarily hard to reproduce a distributed, replicated,
fault-tolerant, infinitely-scaling, self-managing database.  Maybe
Amazon's DynamoDB is getting close - I certainly like the performance
of it, but it still seems to lack a lot of the features of the GAE
datastore.  All other data storage solutions I am familiar with
require a significant amount of maintenance as they scale, and I don't
want to think about that.  I have no ops team and don't ever want one.

The task queue and memcache work well and are nicely integrated. I
like that you can transactionally add a task.  But yeah, these parts
can be replicated elsewhere.

My main points of frustration are:

 * Requests that go to cold start instances.  I think this will
eventually get fixed.

 * $100/mo SSL.  Way too hard on startups, and pushes people away from
the mantra that everything should be ssl all the time.

 * General performance.  Some things are just slower than they should
be.  For example, we (Voost) proxy OSM map tiles because Mapquest
doesn't support HTTPS - everything must be HTTPS or browsers show
mixed content warnings.  Proxying through GAE was visibly slow, and
requests would often fail even with multiple retries.  It's possible
that this is because Akamai (which serves the tiles) is throttling
requests from GAE urlfetch; dunno.  But moving our https tile proxy to
nginx on Heroku made a _world_ of difference.  It's like night and
day.

 * GAE is actually pretty expensive, in a way that isn't so obvious
from the price chart.  The natural tendency is to compare an
"instance" of GAE to an "instance" from some other service, and by
this standard GAE is fairly expensive.  But each GAE instance can
handle a lot less load than an "instance" from almost any other
service, so there is another multiple you wouldn't necessarily expect.
 For most apps the added expense is still tolerable, but for some apps
(ie Richard's game) it's downright pathological.

There are a number of other tricks and difficulties on GAE but there
are almost always workarounds.  It's the nature of working on a large,
clustered, distributed system that some things (eg, aggregating
rapidly changing data) are hard.  Overall I still recommend GAE for
most standard webappy kinds of things... but there are some apps I
would steer away:

 * Apps with a lot of transactional logic are hard.
 * Apps with a lot of ad-hoc query needs are hard.
 * Apps with a lot of rapidly mutating aggregation are hard.

Someday when I have more time I might write a short "GAE Survival
Guide" and sell it for a few bucks as an ebook.

Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[Mos]

Hi Jeff,

min-idle instance is on automatic. Max is on two.
There is at least one request per minute for my "low-traffic app",

>From my perspective a very straight-forward application that shouldn't
have any problems on GAE. (Check: http://www.krisentalk.de/ if you
can speak German. ;) )

I'm surprised that you are still go with GAE for new applications?
You had your own "experiences" from what I saw on this list. ;)

I'm not recommending GAE anymore. I tell my customer to go with other
platforms. After one year following discussions and issues I don't thing
reliability will be improved on GAE in near future (at least for small
and mid-size applications).

Cheers
Mos



On Sat, Aug 18, 2012 at 4:52 PM, Jeff Schnitzer  wrote:
> Have you set the _min_ idle instances to something other than
> automatic?  This setting seems to be especially catastrophic for a
> low-traffic app.
>
> Jeff
>
> On Sat, Aug 18, 2012 at 8:56 AM, Mos  wrote:
>> Add again. The last 48 hours the scheduler creates and closes
>> instances without reason (traffic as usual, no software updates, no
>> special tasks)
>>
>> That's definitely not a "WorkAsIntended" issue!
>>
>> As a result instance hours go up and we have to pay again for GAE's
>> fault.  Great business-model: Let customers pay for bugs and underline
>> it as "WorkAsIntended"!
>>
>> Check: http://code.google.com/p/googleappengine/issues/detail?id=7910
>>
>> On Sat, Aug 4, 2012 at 9:00 PM, Mos  wrote:
>>> Again a not very reliable GAE month:
>>>
>>> Pingdom July
>>>
>>> Uptime   DowntimeOutages Response time
>>> 99.90%  0h 43m 35s  27  466 ms
>>>
>>>
>>> On Wed, Aug 1, 2012 at 11:50 PM, Mos  wrote:
 And again I have to pay for GAE issues:

 On Jul 30 the Frontend Instance Hours goes beyond the free limit.
 First time this week in my application history. Remember:  The application 
 was
 unusable on this day because GAE starts instances like crazy (on low 
 traffic).
 Frontent Instance Hours were consumed of the buggy instance scheduler.

 But to rescue there is another bug in GAE. The billing does not work.
 It's stuck for months and I still read the following message on my
 billing history:
 "We were unable to process your last payment. If the account balance
 ($2.32) is not paid in full by 06/01/2012, this application's quotas
 may be reset to the free levels."

 That's ingenious, Google.  ;)


 On Mon, Jul 30, 2012 at 5:47 PM, Mos  wrote:
> Anyone else seeing issue with GAE instance management?
> In one minute - 10 requests - around 5 instances are started. Old ones
> do not response. New instances are created again and again...
>
> http://code.google.com/p/googleappengine/issues/detail?id=7910
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> 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 google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Instances/Java go crazy

[Jeff Schnitzer]

Have you set the _min_ idle instances to something other than
automatic?  This setting seems to be especially catastrophic for a
low-traffic app.

Jeff

On Sat, Aug 18, 2012 at 8:56 AM, Mos  wrote:
> Add again. The last 48 hours the scheduler creates and closes
> instances without reason (traffic as usual, no software updates, no
> special tasks)
>
> That's definitely not a "WorkAsIntended" issue!
>
> As a result instance hours go up and we have to pay again for GAE's
> fault.  Great business-model: Let customers pay for bugs and underline
> it as "WorkAsIntended"!
>
> Check: http://code.google.com/p/googleappengine/issues/detail?id=7910
>
> On Sat, Aug 4, 2012 at 9:00 PM, Mos  wrote:
>> Again a not very reliable GAE month:
>>
>> Pingdom July
>>
>> Uptime   DowntimeOutages Response time
>> 99.90%  0h 43m 35s  27  466 ms
>>
>>
>> On Wed, Aug 1, 2012 at 11:50 PM, Mos  wrote:
>>> And again I have to pay for GAE issues:
>>>
>>> On Jul 30 the Frontend Instance Hours goes beyond the free limit.
>>> First time this week in my application history. Remember:  The application 
>>> was
>>> unusable on this day because GAE starts instances like crazy (on low 
>>> traffic).
>>> Frontent Instance Hours were consumed of the buggy instance scheduler.
>>>
>>> But to rescue there is another bug in GAE. The billing does not work.
>>> It's stuck for months and I still read the following message on my
>>> billing history:
>>> "We were unable to process your last payment. If the account balance
>>> ($2.32) is not paid in full by 06/01/2012, this application's quotas
>>> may be reset to the free levels."
>>>
>>> That's ingenious, Google.  ;)
>>>
>>>
>>> On Mon, Jul 30, 2012 at 5:47 PM, Mos  wrote:
 Anyone else seeing issue with GAE instance management?
 In one minute - 10 requests - around 5 instances are started. Old ones
 do not response. New instances are created again and again...

 http://code.google.com/p/googleappengine/issues/detail?id=7910
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Hosting static files on GAE and using own domain.

[Raghu Kiran]

Hi Omne,

Please find my answers to your questions below.

Do you I have to do anything special for hosting static HTML pages? 
>>Nope, its far more easier, simpler and less resource consuming than 
servlets and JSP's.

I read on the internet that with Python we should configure a file for 
static files, what about Eclipse? 
>>Yes, python does. I wrote a blog on how to do this in eclipse, the link 
is still under construction, I tried to make the stuff in it as simple as 
possible. Let me know in case you need any support.
http://blog.recurtrix.com/2012/08/host-your-static-website-in-google-for.html
 

I'm going to remove all unwanted files from project folders and add my 
website files and folders to the project and then deploy it. is this what 
should do? 
>>Yes, Thats what you have to do the blog link above should guide you 
with the process in detail.

If I want to point my own domain to my project, should I do it before 
uploading the project or after it? because I noticed GAE has its own domain 
(appspot.com) what if I don't want that my website be available at this 
address too? 
>>You can point to your own domain. http://www.recutrix.com is one such 
hosted app. 
>>You can point it to your own domain after hosting your app.
>> for the last part, I do not have a answer, please post another question 
for it.

Best regards,
Raghu

On Wednesday, 15 August 2012 12:24:15 UTC+5:30, Omne wrote:
>
> Hi, I'm trying to host my website on GAE, it's just a few  HTML page and 
> images. I downloaded the Eclipse and all its required plugins and GAE SDK, 
> I think I were able to upload (deploy) a project successfully, now I can 
> see an index page on myapp.appspot.com wiich says "Hello App Engine!".
>
> Now I have a few questions:
> Do you I have to do anything special for hosting static HTML pages?
> I read on the internet that with Python we should configure a file for 
> static files, what about Eclipse?
> I'm going to remove all unwanted files from project folders and add my 
> website files and folders to the project and then deploy it. is this what 
> should do?
> If I want to point my own domain to my project, should I do it before 
> uploading the project or after it? because I noticed GAE has its own domain 
> (appspot.com) what if I don't want that my website be available at this 
> address too?
>
> Thank you for your help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/E0Us2bZ9l_wJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Instances/Java go crazy

[Mos]

Add again. The last 48 hours the scheduler creates and closes
instances without reason (traffic as usual, no software updates, no
special tasks)

That's definitely not a "WorkAsIntended" issue!

As a result instance hours go up and we have to pay again for GAE's
fault.  Great business-model: Let customers pay for bugs and underline
it as "WorkAsIntended"!

Check: http://code.google.com/p/googleappengine/issues/detail?id=7910

On Sat, Aug 4, 2012 at 9:00 PM, Mos  wrote:
> Again a not very reliable GAE month:
>
> Pingdom July
>
> Uptime   DowntimeOutages Response time
> 99.90%  0h 43m 35s  27  466 ms
>
>
> On Wed, Aug 1, 2012 at 11:50 PM, Mos  wrote:
>> And again I have to pay for GAE issues:
>>
>> On Jul 30 the Frontend Instance Hours goes beyond the free limit.
>> First time this week in my application history. Remember:  The application 
>> was
>> unusable on this day because GAE starts instances like crazy (on low 
>> traffic).
>> Frontent Instance Hours were consumed of the buggy instance scheduler.
>>
>> But to rescue there is another bug in GAE. The billing does not work.
>> It's stuck for months and I still read the following message on my
>> billing history:
>> "We were unable to process your last payment. If the account balance
>> ($2.32) is not paid in full by 06/01/2012, this application's quotas
>> may be reset to the free levels."
>>
>> That's ingenious, Google.  ;)
>>
>>
>> On Mon, Jul 30, 2012 at 5:47 PM, Mos  wrote:
>>> Anyone else seeing issue with GAE instance management?
>>> In one minute - 10 requests - around 5 instances are started. Old ones
>>> do not response. New instances are created again and again...
>>>
>>> http://code.google.com/p/googleappengine/issues/detail?id=7910

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] limiting number of instances / performance of GAE

[Matthias Dahl]

Hello @community.

I am currently evaluating Heroku and GAE for a new service (based on Python 
and Django) that I'd like to offer my clients. In all honesty, I'd like to 
take GAE over Heroku for a few reasons (Safe Harbor certified [important!], 
localized CDN [nice to have], ..., Guido van Rossums works there [:-)] ) 
but the cost structure is a lot less friendly to work with and predict, 
unfortunately.

Based on what I've read, it is not possible to limit the number of 
instances that the scheduler can fire up to deal with the amount of 
traffic? Is this true or has this been fixed? Or has a workaround been 
found yet that works reliably? Is there any other way to limit the amount 
of costs that a single app can cause? This is rather important since 
clients prefer hard facts and prices instead of "well... could be a few 
cents to a few hundred bucks a month". :)

Last but not least: How does the performance of one GAE frontend instance 
compare to a Heroku dyno? Has anyone made any tests so far or can point me 
to a good benchmark somewhere? That would be quite interesting...

Thanks so much in advance for taking the time.

So long,
matthias.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/PNH0sqJ45ZYJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Almost all emails not delivered.

[Prashant Hegde]

Hello!

http://code.google.com/p/googleappengine/issues/detail?id=7974

We have reported a production issue (above) on email delivery failures for our 
app. Kindly look into it. Emails have suddenly stopped (almost all with only 
sporadic emails delivered ) for the last 2 weeks. It was fine earlier.

Best Regards
Prashant


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] The sample application

[Jarosław Szczepanik]

Do you know an application on google app engine that uses google sql and 
opening as a new tab?
Of course, this may not be an application written by Google Inc..
The top menu should appear in the same way I use the applications developed 
by Google Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/czN9WMx0zssJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Next Time you think the scheduler is Broken...

[hyperflame]

Perhaps the 1st, 3rd, and 4th checkout clerks were drinking on the
job? Complain to Google's HR department :-)




On Aug 18, 3:23 am, "Drake"  wrote:
> I'm pretty sure the most efficient check out system is not to have one
> cashier handle 21k customers in 8 hours and the register that was open 15
> minutes sooner handle only 25.
>
> Or to have a 4th lane open for 57 requests.
>
> No combination of this was optimal for the 15 minute billing increment.
> Even if those 25 requests are 14 min 59 sec apart, 25 /4 is only 6 hours and
> change.
>
> From: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer
> Sent: Friday, August 17, 2012 11:58 PM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Next Time you think the scheduler is
> Broken...
>
> What are you trying to say here?
>
> Jeff
>
> On Sat, Aug 18, 2012 at 2:08 AM, Drake  wrote:
>
> So the next time you think the Check out line analogy is flawed.. I think it
> is accurate but I'm not sure the scheduler does what we all expect..
>
> This is about 100 Gigs worth of xfer in 70k Requests a day.
>
> 0.000
>
> 0.0 ms
>
> 57
>
> 0
>
> 1:30:37
>
> 32.4 MBytes
>
>   c
> 61b117c8ba9543aab3ecfc850baacd6dd4dcf&filter_type=regex&date_type=now&limit =
> 20&view=Search> View Logs
>
> Description: Dynamic IconDynamic
>
> 1.683
>
> 21.2 ms
>
> 21023
>
> 0
>
> 7:50:49
>
> 51.0 MBytes
>
>   c
> 61b117cceee87a5c8b3c26bfdef9393196486&filter_type=regex&date_type=now&limit =
> 20&view=Search> View Logs
>
> Description: Dynamic IconDynamic
>
> 0.000
>
> 0.0 ms
>
> 266
>
> 0
>
> 8:04:53
>
> 31.6 MBytes
>
>   c
> 61b117c5937b082ee32869e0155dd6dd48ffb&filter_type=regex&date_type=now&limit =
> 20&view=Search> View Logs
>
> Description: Dynamic IconDynamic
>
> 0.000
>
> 0.0 ms
>
> 25
>
> 0
>
> 8:11:32
>
> 31.0 MBytes
>
>   c
> 61b117c320e688017ba4d38f95222d9430596&filter_type=regex&date_type=now&limit =
> 20&view=Search> View Logs
>
> Description: Dynamic IconDynamic
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com
>  .
> 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 google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/google-appengine?hl=en.
>
>  image001.png
> 1KViewDownload

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

RE: [google-appengine] Next Time you think the scheduler is Broken...

[Drake]

I'm pretty sure the most efficient check out system is not to have one
cashier handle 21k customers in 8 hours and the register that was open 15
minutes sooner handle only 25.

 

Or to have a 4th lane open for 57 requests.

 

No combination of this was optimal for the 15 minute billing increment.
Even if those 25 requests are 14 min 59 sec apart, 25 /4 is only 6 hours and
change.  

 

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer
Sent: Friday, August 17, 2012 11:58 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Next Time you think the scheduler is
Broken...

 

What are you trying to say here?

 

Jeff

On Sat, Aug 18, 2012 at 2:08 AM, Drake  wrote:

So the next time you think the Check out line analogy is flawed.. I think it
is accurate but I'm not sure the scheduler does what we all expect..

 

This is about 100 Gigs worth of xfer in 70k Requests a day. 

 

 


0.000

0.0 ms

57

0

1:30:37

32.4 MBytes

 
 View Logs

Description: Dynamic IconDynamic



1.683

21.2 ms

21023

0

7:50:49

51.0 MBytes

 
 View Logs

Description: Dynamic IconDynamic



0.000

0.0 ms

266

0

8:04:53

31.6 MBytes

 
 View Logs

Description: Dynamic IconDynamic



0.000

0.0 ms

25

0

8:11:32

31.0 MBytes

 
 View Logs

Description: Dynamic IconDynamic



 

 

 

-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
 .
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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>