Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI am not sacrificing all modularity because I am proposing to process my source code using a tool prior to deployment, very much in the way that modern javascript tools combine, split and optimise javascript prior to deployment to that actual browser. It's a fine idea to say "write your code to only import what you need", but then that precludes using the 300 od source files in core django, not including contrib modules, external libraries, and anything I might write. Besides, you often do want to import a lot of code because you actually do use it.
      singulars
    2. CONick, you work at Google, can you describe the process of loading deploying user code on App Engine please? It's not merely the cost of disk seeks as multiple modules are loaded, as in a conventional setup, because all user code is not deployed to all instances simultaneously. How is it actually done? How is it actually done? Are all files deployed together, one at a time, or in batches? How does the custom zip code work? when you load one module from a zip, are all module within loaded, or does it happen on demand? etc...
      singulars
    3. COIf having '300 odd' source files is a problem for doing on-demand importing, it's equally problematic if you want to concatenate them all - either would require substantial modifications. The problem with using a large framework like Django is that, as you've observed, it takes a long time to import. I doubt you're using more than 20% or so of the modules for any given request, though.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload