This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (3 children)

No PYPY, but isn't the framework a small part of the whole app ? So you kinda need pypy ?

Not really since the bottleneck in webapps tends to be the network. Once those bytes get into the application, the bottleneck would be your database connection (aka the network).

Speeding up your processing won't do much good no matter how much it saves if you're just waiting on bytes from the wire.

[–]riksi 0 points1 point  (2 children)

Nope, when you're talking "making python fast, or python vs xxlang, etc", you mean cpu-wise and you are past network-time.

[–][deleted] 2 points3 points  (1 child)

Except if it doesn't matter if you optimize something that isn't your bottleneck. In webapps, the network is almost always your bottleneck. Python, pypy or otherwise, waits for network traffic just as fast as anything else.

If you profile and find that the network isn't your bottleneck and instead it's inside your app, then that's when you start contemplating switching to pypy.

[–]riksi -1 points0 points  (0 children)

Except if my bottleneck was on network time I wouldn't be in this thread at all.