Nuitka: An extremely compatible Python compiler

Post by adamdusty » Thu, Sep 02, 2021, 4:36 PM UTC

spenczar5 wrote: post #43

Eikon wrote: post #35

Earlier quoted context omitted.

This argument is so tiring. That's part of why websites are so slow despite having insane hardware at their disposal. At my company, for a web app we run in production, we strive to get every response out of our infrastructure in under a millisecond, everything above that except for a few select endpoints is considered as a bug. By using sensible technology choices, it's not even that hard to do. A RDMS like postgres…

Right, I agree. My question is “what application is constrained by interpreter overhead.” It should be faster than milliseconds for almost any code, I would think. I am agreeing with you, I don’t understand your response.

Post by knxl » Thu, Sep 02, 2021, 5:01 PM UTC

Post by pjmlp » Thu, Sep 02, 2021, 5:29 PM UTC

eatonphil wrote: post #23

pjmlp wrote: post #19

Earlier quoted context omitted.

Not really what you are after, but it does use AOT (via generated C++ code). https://arcade.makecode.com/ https://makecode.com/language

> In case of microcontrollers, PXT programs are compiled in the browser to ARM Thumb assembly, and then to machine code, resulting in a file which is then deployed to the microcontroller, usually via USB mass-storage interface. Looks like the only compilation strategy is directly to ARM Thumb assembly or did I miss something?

Post by bb101 » Thu, Sep 02, 2021, 5:50 PM UTC

Eikon wrote: post #35

spenczar5 wrote: post #32

Earlier quoted context omitted.

What sort of web applications do you work on where Python interpreter speed is the limiting factor? Usually, those applications are constrained by network throughput and context switches and page faults.

This argument is so tiring. That's part of why websites are so slow despite having insane hardware at their disposal. At my company, for a web app we run in production, we strive to get every response out of our infrastructure in under a millisecond, everything above that except for a few select endpoints is considered as a bug. By using sensible technology choices, it's not even that hard to do. A RDMS like postgres…

Post by [deleted] » Thu, Sep 02, 2021, 6:05 PM UTC

bb101 wrote: post #57

Eikon wrote: post #35

Earlier quoted context omitted.

This argument is so tiring. That's part of why websites are so slow despite having insane hardware at their disposal. At my company, for a web app we run in production, we strive to get every response out of our infrastructure in under a millisecond, everything above that except for a few select endpoints is considered as a bug. By using sensible technology choices, it's not even that hard to do. A RDMS like postgres…

What web/app stack are you using to fulfill <1ms responses?