Static File Questions

[MajorProgamming]

Just a few questions on static files:

1. Does serving a static file cost CPU usage?

2. Does having a large number of static files (let's say like 700)
have _any_ effect on performance of page serving [similarly, does
having a lot of mappings affect performance]?

3. When a python script reads a file off the app's filesystem (like a
template html file), is that any faster than a get_by_key on the
datastore? [i.e. filesystem vs. bigtable performance]?

4. Will the paid version of Google App Engine allow over 1000 files
and/or larger than 1MB files (or entities)?

Thanks,

[N. Rosencrantz]

Reversibly breaking and remaking larger than 1MB files persistently
storing max 1 MB chunks, gae http get and post support the larger. The
gae http transport as it is handles larger files. The 1MB limit only
limits the entities, not the transport.

[MajorProgamming]

I'm not sure I understand you. Which question # were you trying to
answer?

[N. Rosencrantz]

example: upload a 2 MB file through a html form, split it serverside
into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
It's inconvenient yet a method to serve large files with no difference
towards the client.

[MajorProgamming]

I don't mean when the user uploads files. I mean when I do (i.e.
through appcfg.py). Does it hurt performance if GAE has like 700
static files from me...?

[James Ashley]

On Jan 9, 3:34 pm, niklasr <nikla...@gmail.com> wrote:
> example: upload a 2 MB file through a html form, split it serverside
> into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
> It's inconvenient yet a method to serve large files with no difference
> towards the client.

Is this a new development? Last I checked, a request > 1MB would just
fail. It seems like streaming BLOBs like this might work, if you're
clever enough, but...

Has this been cleared up and I missed it? (Entirely possible, and
desirable, of course)

Regards,
James

[N. Rosencrantz]

On Jan 25, 6:22 am, James Ashley <james.ash...@gmail.com> wrote:
> On Jan 9, 3:34 pm, niklasr <nikla...@gmail.com> wrote:
>
> > example: upload a 2 MB file through a html form, split it serverside
> > into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
> > It's inconvenient yet a method to serve large files with no difference
> > towards the client.
>
> Is this a new development?  Last I checked, a request > 1MB would just
> fail.

It's probably been possible since gae start, only too complicated.
Requests > 1MB from html upload form are read:

file = self.request.POST.get('file').file.read()
len = file.__len__()

or in MB

len = file.__len__()/(1024.0*1024.0)

With above code I can determine filesizes > 1 MB. Then storing and
serving the larger files requires partitioning at max 1 MB.

best regards
Niklas