tag:blogger.com,1999:blog-3971202189709462152.post8755773725359396485..comments2024-03-11T12:50:02.036+01:00Comments on PyPy Status Blog: VM summit: nice to see friendly competitionCarl Friedrich Bolz-Tereickhttp://www.blogger.com/profile/00518922641059511014noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-3971202189709462152.post-11238085943993204682009-05-29T00:35:16.384+02:002009-05-29T00:35:16.384+02:00Maciej said: "It would be a good speedup for a lot...Maciej said: "It would be a good speedup for a lot of people though (of course we aim to speed up stuff according to JS engines ;)"<br /><br />What ever happend to the "secret goal" of being faster than c...?Luishttps://www.blogger.com/profile/01147433030878927988noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-56445886336724010722009-03-28T14:34:00.000+01:002009-03-28T14:34:00.000+01:00Maciej, this is a reply posted on the project's FA...Maciej, this is a reply posted on the project's FAQ page:<BR/><BR/> Comment by collinw, Today (8 hours ago)<BR/><BR/>luismgz: translating Python to Javascript would be easy to implement for about 80% of the language, but you'd hit a wall in implementing that last 20%. Just ask the Jython, PyPy? and IronPython? teams how hard 100% compatibility is. They've done some really heroic work to implement every dark and musty corner of the language, and I think they'd be the first to tell you that it's easy to get something like the Fibonacci function working, but things like metaclasses are a different story. We hope to side-step that by reusing as much of CPython as possible.<BR/><BR/>Psyco's claimed benefits of 100x speed-up on algorithmic code is rarely seen in real applications. It can certainly be used to optimize hotspots that fit Psyco's profile, but in examining the performance of some Google applications that use Psyco, we found that they see only a ~10% improvement in overall CPU usage. While that might be a valuable savings for some applications, it's not 100x, nor even the 2-4x low-end estimate that I've seen in the Psyco docs.<BR/><BR/>Are our performance goals too modest? We don't think so. Our team is small -- only two full-time engineers -- and we want to allow for unexpected surprises along the way. We feel that 5x is a good goal for the time being, especially given that we may need to make changes to LLVM along the way. If things go astoundingly well, we may raise those numbers, but for now, we're comfortable with our stated goals.Luishttps://www.blogger.com/profile/01147433030878927988noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-87229957130907407012009-03-28T14:28:00.000+01:002009-03-28T14:28:00.000+01:00The exact meaning of 5x is I *think* "5x on tests ...The exact meaning of 5x is I *think* "5x on tests derived from google internal apps". It's a bit little, but note that the great speedups of JS engines are for simple algorithmic code (the one that psyco speedups great).<BR/><BR/>It would be a good speedup for a lot of people though (of course we aim to speed up stuff according to JS engines ;)<BR/><BR/>Cheers,<BR/>fijalMaciej Fijalkowskihttps://www.blogger.com/profile/11410841070239382771noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-53453181905952153012009-03-28T14:22:00.000+01:002009-03-28T14:22:00.000+01:00This comment has been removed by the author.Maciej Fijalkowskihttps://www.blogger.com/profile/11410841070239382771noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-19208060276105824242009-03-28T02:51:00.000+01:002009-03-28T02:51:00.000+01:00I don't understand: These days, Google's v8 claims...I don't understand: These days, Google's v8 claims to be 56x faster than common javascript, tracemonkey is in the same league, as well as nitro, etc. Way before, psyco sped up python (theoretically) up to c's speed for algorithmic code, and up to 4x for common code.<BR/><BR/>Now Unladen Swallow aims to "only" 5x speed up. Isn't it to little, seeing what the above projects are getting nowadays?<BR/>Or am I getting confussed by their terminology? (what's exactly the meaning of 5x here?).Luishttps://www.blogger.com/profile/01147433030878927988noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-10841859913930254942009-03-27T03:24:00.000+01:002009-03-27T03:24:00.000+01:00Anonymous#1, this is extremely valuable note to ta...Anonymous#1, this is extremely valuable note to take in an open source world, you know ;-)<BR/><BR/>PyPy folks, keep up the good work!<BR/><BR/>But... Sometimes I miss updates on this blog. Not in the sense that you slack on it, but in the sense that I miss some "technicaly intermediate" updates when there are no news on breathrouths.<BR/><BR/>One thing I miss most is the retro style articles on how some things that are "established" now got to be this way. The design by evolution things. Stuff that both educates and helps to get acquainted with the code one might like to hack one day.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-4412992959347181742009-03-27T03:01:00.000+01:002009-03-27T03:01:00.000+01:00We were a bit confused about usage of the term JIT...<I>We were a bit confused about usage of the term JIT, because as far as we understood, it's going to be upfront compilation into LLVM.</I><BR/><BR/>The LLVM supports JIT, so compiling Python into LLVM bytecode will give JIT for free.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-71712430100046802372009-03-27T02:16:00.000+01:002009-03-27T02:16:00.000+01:00All three of the primary developers are Google emp...All three of the primary developers are Google employees.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-48756623960163469342009-03-26T15:21:00.000+01:002009-03-26T15:21:00.000+01:00So Google has launched the unladen swallow project...<I>So Google has launched the unladen swallow project with this first goal</I><BR/><BR/>I'm not sure this is a Google project. It's hosted on Google code for sure, but anyone can do that.Anonymousnoreply@blogger.com