i've got some code for this from a recent project . hit me up .
log individual events, then run map reduce to aggregate into time slices also
by field values to create preagrregrated counts .
querying is not as nimble as say mongo, so this works, but a few extra steps
--
You received this mess
It surprises me at how the cost of disk is getting applied everywhere.. Disk is
fuckin cheap!! I'd rather pay where paying counts
--
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.goog
This is awesome.. I like how you kept the code succinct and terse
--
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/-/GkD9-qMeFyYJ.
To post to this gro
Not directly answering the question, I'm posing another, why the eff are you
running instances in such a manner for such little qps
Also, I can also suggest that at that low of qps, you could stand to
substantially optimize the work you're doing reading data from the data store,
which will
*Richard Watson's *post was money.. ackkk.. someone unwittingly let the
cache-control header slip into a base request handler.. thnx everyone..
On Sunday, April 29, 2012 12:53:15 AM UTC-7, Richard Watson wrote:
>
> What if Gregory put (e.g.) Cloudflare in front of the app and used it to
> fetch
by bingo i meant that was the request with the /? worked indeed..
dare i ask on options to cache bust?
On Fri, Apr 27, 2012 at 12:53 PM, Gregory Nicholas <
nicholas.g.greg...@gmail.com> wrote:
> yep.. bingo.. what are my options from here?
>
>
>
> On Fri, Apr 27, 201
gt; > has been cached elsewhere in Google's network. If you responded with
> > cache-control: public with a max-age of something, it may be cached
> > until that expires.
> > Without futher info (such as an appid or the domain), it's hard to
> > tell what
is there currently a way to only deploy certain, or only static files?
this is what i'm currently facing, and hoping to use a selective
deploy feature for:
- my app is currently managing a couple dozen automated system emails
- created them as django templates to reduce maintenance overhead
- som
if it's as bad as 6 to 8 seconds, have you looked at creating a list
of string for the property names? i know its more maintenance
overhead, but might be worth the tradeoff..
ex:
class SerializableModel(object):
serializable = []
def to_json(self):
result = []
for x in self.serializ
