Comments on: Scaling Python on the Web http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/ Because eventually I'll be right. Theoretically. Fri, 16 Dec 2011 15:14:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: nathan http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/comment-page-1/#comment-205 nathan Tue, 06 Mar 2007 13:35:57 +0000 http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/#comment-205 "easy but slow... compared to Java"? I'll buy the easy part, but I wouldn't have pointed to Java as my exemplar of speed. I don't think Java is slow, but then I don't think Python is slow, either. I think both are "slower than C", but that's just a comparative statement, not absolute. “easy but slow… compared to Java”?

I’ll buy the easy part, but I wouldn’t have pointed to Java as my exemplar of speed. I don’t think Java is slow, but then I don’t think Python is slow, either. I think both are “slower than C”, but that’s just a comparative statement, not absolute.

]]> By: BLA http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/comment-page-1/#comment-206 BLA Tue, 06 Mar 2007 11:19:37 +0000 http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/#comment-206 Each tool has its pros & cons. Each problem has its appropriate tools. Wrong mixes of problem & tools = bad results. Caching is hard, it's not a panacea, Python is easy but slow (compared - for example - to Java). Do you want fast development & fast code? Use Python, optimize it with your own C extensions. Yes, "optimize only what you need". Optimize only that, only with C. And only if you can't make your *algorithms* better, and can't design your *database* more carefully. And don't use CGI, if possible. SHORTLY: Python, no CGI, optimized database & algorithms = fast development & good codebase. ONLY AFTER THAT tune your code & setup with C, caching, load balancing = hard part of development. Each tool has its pros & cons. Each problem has its appropriate tools. Wrong mixes of problem & tools = bad results. Caching is hard, it’s not a panacea, Python is easy but slow (compared – for example – to Java).

Do you want fast development & fast code? Use Python, optimize it with your own C extensions. Yes, “optimize only what you need”. Optimize only that, only with C. And only if you can’t make your *algorithms* better, and can’t design your *database* more carefully. And don’t use CGI, if possible.

SHORTLY: Python, no CGI, optimized database & algorithms = fast development & good codebase. ONLY AFTER THAT tune your code & setup with C, caching, load balancing = hard part of development.

]]> By: ingo http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/comment-page-1/#comment-204 ingo Sat, 03 Mar 2007 18:29:53 +0000 http://yergler.net/blog/2007/02/24/scaling-python-on-the-web/#comment-204 This is somewhat of a pet peeve, so excuse my rambling, but I miss an "outstanding problems" section for caching. Caching is /hard/, especially when dealing with dynamic web-sites such as CMS-driven sites. I couldn't care less that 95% get a fast response through caching if my 5% of editing interactions are slow. Caching is not a panacea and while the whole stuff about "optimize only what you need" is absolutely true and I dearly value the development speed that Python gives me, there are faster interpreters out there. This is somewhat of a pet peeve, so excuse my rambling, but I miss an “outstanding problems” section for caching. Caching is /hard/, especially when dealing with dynamic web-sites such as CMS-driven sites. I couldn’t care less that 95% get a fast response through caching if my 5% of editing interactions are slow.
Caching is not a panacea and while the whole stuff about “optimize only what you need” is absolutely true and I dearly value the development speed that Python gives me, there are faster interpreters out there.

]]>