Re: [google-appengine] Go AppEngine vs Java AppEngine

[Shilendra Sharma]

Hi. Luke

You use the JAVA for  google app engine
Regards & Thanks
Shilendra Sharma
+919891343808
shilen...@gmail.com

On Wed, Sep 5, 2012 at 6:35 PM, Luke Mauldin <lukem...@gmail.com> wrote:

All,

I have a new development project starting and I plan on using AppEngine.  I have the choice of using either Go or Java as my primary language and I have experience using both of them.  From what I can see, more AppEngine services are available for Java but the list of supported services for Go is growing.  Does anyone have any feedback on comparing the languages in the App Engine environment?  I am specifically interested in knowing if anyone has experienced substantial performance improvements migrating their Java App Engine projects to use Go?

Luke

--
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/-/7xgB-H8E_6cJ.
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.

[Kyle Finley]

Luke & Shildendra,

I think one major advantage of Go is the instance startup time. In my experiences it's always less than 1 second. Whereas startup time for Java instance cause much unnecessary stress. Just search the list -- you will find thread upon thread where it is being discussed.

I suspect that Go will win on raw number crunch over Java, too, but, I haven't tested it, and it may depend upon the task.

Concurrency, the one area where you would expect Go to shine, you might be surprised. All App Engine instances are capped at 10 in flight requests. Therefore, the gains that you would see in fewer instances will be severely reduced. This cap is major issue for all languages though, and I'm confident that it will be resolved soon. Here's the issue on the issue tracker if you would like to star it:Allow instance to handle more then 10 requests.

- Kyle

Because, currently, all instances are capped at 10 in flight request it's , but 

[Shilendra Sharma]

Hi..Kyle

As you told this is right but not fully comfort in terms of google app engine

 
Regards & Thanks
Shilendra Sharma
+919891343808
shilen...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/0fPwChJDb10J.

[Drake]

We found that Go runs neck and Neck with Python. It has less penalty for threading. It is slower on RegEx.

 

Java is more memory intensive. And depending on your Frameworks is often slower to warm up.

 

Go has less documentation and less sample code so if you wander off the beaten path you are on your own.

[Barry Hunter]

On Wed, Sep 5, 2012 at 5:35 PM, Shilendra Sharma wrote:

>
> As you told this is right but not fully comfort in terms of google app

What? Care to elaborate on that claim?

[Kyle Finley]

Excellent point Brandon. Memory usage in Go is a huge win. Where a python app my use 40Mb an equivalent Go app would use 7Mb. This leaves more room for a cache.