It's not clear what the problem is. Do you mean you do not want new
instances to spin up?
On Thursday, April 30, 2015 at 5:20:54 AM UTC-4, aswath wrote:
>
> Hi,
> I just want to raise this issue again. Its discussed many times. Any
> recommendations or settings to fix this. I have tried differ
It looks like you are including a semicolon after the appid. I get the same
error if I include it as well. The 400 response is likely the result of
trying to parse an invalid token.
On Thursday, April 30, 2015 at 9:01:48 AM UTC-4, matt baker wrote:
>
> python appcfg.py --
> no_cookies -A appid;
On Friday, May 1, 2015 at 4:13:03 PM UTC-7, Waleed wrote:
>
> My app was also rolled back to 1.9.19 yesterday. Then later it was back on
> 1.9.20, but the error seems to have been fixed. I also got email
> confirmations from customers that they're not seeing this problem any more.
> Great team w
Thanks a lot for all your input
I've cranked up the default_expiration to 60d, yet I doubt it will have any
effect, unless there is a cut-off structure and 1h is below that cut-off,
the majority of these images are consumed by an API which is pretty much a
black-box
My monthly usage is around
Maybe consider dumping the images into Cloud Storage and serve from there?
If the images are static, using Cloud Storage could save you money on
multiple fronts:
1. Cheaper bandwidth
2. Cheaper storage cost
-- Joe
On Sat, 2 May 2015 at 12:59 Kaan Soral wrote:
> Hi everyone
>
> I recently notice
Some thoughts:
You could serve images from Cloud Datastore instead of from App Engine. You
mention that bandwidth costs dominate instance time, but it should help a
bit. If my math is correct, you're serving at least 250GB per day, so
provided you're serving mostly to the US, the you'd get some
Use AWS. 30% is a quite a difference. Also you would have more control over
headers and images can be closer to end customers - would not help with
costs but it's nice.
Increasing cache time if you can. We set caching for over a month.
Theoretically they can be cached by proxies as well (*but pr
Hi everyone
I recently noticed a bump in costs after improving the static image quality
of my app, this bumped the daily bandwidth costs from ~7$'s to 20$+'s
Overall there are ~200 statically served images, I tried reducing the
quality of png's and turning them into jpg's, yet it degrades the i
