You use one backend instance to cater for larger memory speed requirements. Depending on throughput requirements you can configure the instances property to run more than one instance in that higher class.
Step 1. Configure backends.yaml backends: - name: medium class: B2 instances: 1 options: dynamic Step 2. Enqueue a task with target (using the python defer library in this example): defer(doSomethingBigger, _queue='some-queue-for-big-stuff', _target='medium') Step 3. Profit On Wednesday, November 28, 2012 3:30:51 PM UTC-5, Emanuele Ziglioli wrote: > > Thank you for the suggestion, > > I'm not sure if I understand, which one these two: > 1. You use one backend instance to cater for larger memory/speed > requirements > 2. You use one backend instance to spin multiple F1 and/or F2 task queues > because backends allow you to > > > On Thursday, 29 November 2012 08:45:16 UTC+13, Andy wrote: >> >> Setting the "instances" option in the backends.yaml allows it to scale up >> that value. 15m penalty is well worth it because 99% of our traffic fits >> in an F1 but we had to run F2s previously to allow the 1% of the tasks to >> succeed. As a result our costs are roughly half as much. >> > > >>> -- 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/-/uGOolhR5ChYJ. 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.
