Thank you for a great release!

Heavy frameworks like Spring MVC can be loaded really fast if you
serialize the context into cache/datastore. Unfortunately this is not
easy to do and I don't know if SpringSource is planning on making it
easier.

A blog post like that was bound to be published sooner than later.
What we need now is a counter post ;)

Cheers,
Viðar

On Mon, Nov 22, 2010 at 6:20 PM, Ikai Lan (Google)
<[email protected]> wrote:
> Hey,
> A couple of questions were brought up in this thread. I'll do my best to
> answer them:
> - YES, task queues and cron jobs will now have a 10 minute limit, increased
> from 30 seconds. Note that you still want to favor lots of small, quick
> tasks when possible.
>
> - I need to verify the behavior, but the reason you will want to prefer
> shorter tasks is because these are scaled along with your user facing tasks
> = higher task throughput. Scaling of slow tasks works differently and you
> will ultimately receive lower throughput for those jobs, so you'll want to
> reserve those queues for work where you get a lot of payoff for 10 minute
> tasks but don't need the 50/qps per queue throughput of fast running tasks.
> - Yes, you will still have a 1mb limit upload limit.
> - App Instance startup still has a 30 second limit. We've explored what it
> would take to change this, but it's our understanding that even the heaviest
> of heavy frameworks (Spring MVC) can initialize in under 30 seconds. You'll
> still want to favor lazy initialization when possible. Again, we need to do
> more exploration here. The long term solution may be to increase the
> initialization deadline. Right now we're unsure of what'll happen if we do
> this, and we're unsure of whether this will be a healthy decision for the
> serving infrastructure overall.
> - The max deadline has not changed for URLFetch. There are lots of reasons
> to be optimistic, however. It's in our plans to remove limits where we can -
> and document the tradeoffs of doing so.
> I don't have an ETA (do I ever?) for the release, but as with previous
> releases, the go-live date is usually in the ballpark of weeks after the
> prerelease SDK is posted. Just keep in mind that 1.4.0 is a HUGE
> undertaking, so I'd leave a little more runway for when it'll go live. As
> usual, testing the prerelease SDK and giving us your feedback helps us ship
> it faster.
> Also - I saw the blog post. It's unfortunate, since the author of that post
> posted on the forums a few times and received a lot of help from both us and
> members of the community. I think it's easier to remember the negative. He
> sounded and still sounds like someone who knows what he is talking about, so
> if he couldn't find the documentation about limits, that means we can do a
> better job of surfacing them right after someone completes the "Guestbook"
> tutorial, because he's sure as heck not the only one who has/is/will be
> surprised by these limitations. I'll look more closely at his post and model
> either my own blog post or some official docs after it. I'll fiercely
> disagree with anyone that says App Engine is not a good platform for serious
> businesses or that Google doesn't invest in it. Of course we do: we launch
> stuff on App Engine all the time. There are small teams at Google just as
> there are large teams, and they come to App Engine for all the reasons you
> all do.
> Hope this helps. Keep posting feedback. I'm seeing only 100-200 downloads of
> the prerelease SDKs, which you can download here:
> http://code.google.com/p/googleappengine/downloads/list
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blogger: http://googleappengine.blogspot.com
> Reddit: http://www.reddit.com/r/appengine
> Twitter: http://twitter.com/app_engine
>
>
> On Sat, Nov 20, 2010 at 1:54 AM, DAndrea <[email protected]>
> wrote:
>>
>> Fantastic release!
>>
>> I wanted a clarification about URLFetch.
>> With a response size limit increased up to 32mb I also would expect a
>> new max deadline that seems not changed (10 seconds)
>> Thanks!
>>
>> On Nov 18, 11:27 pm, "Ikai Lan (Google)" <[email protected]>
>> wrote:
>> > Hey everyone,
>> >
>> > I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get
>> > it
>> > from the Google Code project:
>> >
>> > http://code.google.com/p/googleappengine/downloads/list
>> >
>> > We're still working on the docs and will have them ready for the final
>> > release, so if there are any questions about how to use the new
>> > features,
>> > feel free to ask on this thread and I'll do my best to clarify them. The
>> > release notes are below. This is an EXCITING release:
>> >
>> > Python
>> > ------------
>> > - The Always On feature allows applications to pay and keep 3 instances
>> > of
>> > their
>> >   application always running, which can significantly reduce application
>> >   latency.
>> > - Developers can now enable Warmup Requests. By specifying  a handler in
>> > an
>> >   app's app.yaml, App Engine will attempt to to send a Warmup Request to
>> >   initialize new instances before a user interacts with it. This can
>> > reduce
>> > the
>> >   latency an end-user sees for initializing your application.
>> > - The Channel API is now available for all users.
>> > - Task Queue has been officially released, and is no longer an
>> > experimental
>> >   feature. The API import paths that use 'labs' have been deprecated.
>> > Task
>> > queue
>> >   storage will count towards an application's overall storage quota, and
>> > will
>> >   thus be charged for.
>> > - The deadline for Task Queue and Cron requests has been raised to 10
>> > minutes.
>> >   Datastore and API deadlines within those requests remain unchanged.
>> > - For the Task Queue, developers can specify task retry_parameters in
>> > their
>> >   queue.yaml.
>> > - Metadata Queries on the datastore for datastore kinds, namespaces, and
>> > entity
>> >   properties are available.
>> > - URLFetch allowed response size has been increased, up to 32 MB.
>> > Request
>> > size
>> >   is still limited to 1 MB.
>> > - The Admin Console Blacklist page lists the top blacklist rejected
>> > visitors.
>> > - The automatic image thumbnailing service supports arbitrary crop sizes
>> > up
>> > to
>> >   1600px.
>> > - Overall average instance latency in the Admin Console is now a
>> > weighted
>> >   average over QPS per instance.
>> > - The developer who uploaded an app version can download that version's
>> > code
>> >   using the appcfg.py download_app command. This feature can be disabled
>> > on
>> >   a per application basis in the admin console, under the 'Permissions'
>> > tab.
>> >   Once disabled, code download for the application CANNOT be re-enabled.
>> > - Fixed an issue where custom Admin Console pages did not work for
>> > Google
>> >   Apps for your Domain users.
>> > - Allow Django initialization to be moved to appengine_config.py to
>> > avoid
>> >   Django version conflicts when mixing webapp.template with pure Django.
>> >    http://code.google.com/p/googleappengine/issues/detail?id=1758
>> > - Fixed an issue in the dev_appserver where get_serving_url did not work
>> >   for transparent, cropped PNGs:
>> >    http://code.google.com/p/googleappengine/issues/detail?id=3887
>> > - Fixed an issue with the DatastoreFileStub.
>> >    http://code.google.com/p/googleappengine/issues/detail?id=3895
>> >
>> > Java
>> > ---------
>> > - The Always On feature allows applications to pay and keep 3 instances
>> > of
>> > their
>> >   application always running, which can significantly reduce application
>> >   latency.
>> > - Developers can now enable Warmup Requests. By specifying  a handler in
>> > an
>> >   app's appengine-web.xml, App Engine will attempt to to send a Warmup
>> > Request
>> >   to initialize new instances before a user interacts with it. This can
>> > reduce
>> >   the latency an end-user sees for initializing your application.
>> > - The Channel API is now available for all users.
>> > - Task Queue has been officially released, and is no longer an
>> > experimental
>> >   feature. The API import paths that use 'labs' have been deprecated.
>> > Task
>> > queue
>> >   storage will count towards an application's overall storage quota, and
>> > will
>> >   thus be charged for.
>> > - The deadline for Task Queue and Cron requests has been raised to 10
>> > minutes.
>> >   Datastore and API deadlines within those requests remain unchanged.
>> > - For the Task Queue, developers can specify task retry-parameters in
>> > their
>> >   queue.xml.
>> > - Metadata Queries on the datastore for datastore kinds, namespaces, and
>> > entity
>> >   properties are available.
>> > - URL Fetch allowed response size has been increased, up to 32 MB.
>> > Request
>> > size
>> >   is still limited to 1 MB.
>> > - The Admin Console Blacklist page lists the top blacklist rejected
>> > visitors.
>> > - The automatic image thumbnailing service supports arbitrary crop sizes
>> > up
>> > to
>> >   1600px.
>> > - Overall average instance latency in the Admin Console is now a
>> > weighted
>> >   average over QPS per instance.
>> > - Added a low-level AysncDatastoreService for making calls to the
>> > datastore
>> >   asynchronously.
>> > - Added a getBodyAsBytes() method to QueueStateInfo.TaskStateInfo, this
>> > returns
>> >   the body of the task state as a pure byte-string.
>> > - The whitelist has been updated to include all classes from
>> > javax.xml.soap.
>> > - Fixed an issue sending email to multiple recipients.
>> >    http://code.google.com/p/googleappengine/issues/detail?id=1623
>> >
>> > As usual, we value your feedback, so don't hesitate to evaluate these
>> > SDKs
>> > and let us know. Be mindful that the server-side components have not
>> > been
>> > deployed yet, so uploaded code shouldn't work.
>> >
>> > Happy coding!
>> >
>> > --
>> > Ikai Lan
>> > Developer Programs Engineer, Google App Engine
>> > Blogger:http://googleappengine.blogspot.com
>> > Reddit:http://www.reddit.com/r/appengine
>> > Twitter:http://twitter.com/app_engine
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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.

Reply via email to