-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Performance #830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For now, short story is: the implementation follows a similar basic design to CPython, with none of its current optimizations (and some aspects done in vastly inefficient ways). It can be anywhere from 5x to 100x slower for now. AFAIK the focus for now is to make it satisfyingly correct and complete; performance will come later. |
@adrian17 Is there any potential performance edge to be gained with Rust at some point? |
as I understand it may be possible to get a more efficient and predictable GC due to Rust's memory model. and it may be possible to get around the GIL with minimal performance degradation for the same reason. But afaik these are only assumptions at this point. In truth baring a JIT approach to the VM there is little to no performance to be gained over CPython just by using Rust. however, it has other benefits: Safer language extension, and the ability to bind the runtime into other Rust applications without linking C code. |
@infosisio See #846 ResultOS: macOS High Sierra 10.13.5 (17F77)
|
Update: ResultLaptop: MacBook Pro (Retina, 15-inch, Mid 2015)
RustPython vs CPython:
|
How does the performance of RustPython compare (or will compare) with CPython or PyPy?
The text was updated successfully, but these errors were encountered: