-
Notifications
You must be signed in to change notification settings - Fork 29
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
Versions & Releases #13
Comments
performance is probably a non-issue. I can't see this taking more than 10ns/it. Certainly not in the short term where we'll only have basic features. C support as I mentioned elsewhere is going to be a completely different repo (tqdm.c) that you guys are all welcome to create and manage. |
@casperdcl One of the selling points of python tqdm was speed. C++ is faster so to maintain the same relative speediness we'll need to reduce nanoseconds/iteration to C++ fast, vs. Python fast. |
from cpp test:
python equivalent: >>> import tqdm; [0 for _ in tqdm.trange(0, 8192, 2)]
|
@casperdcl 2.3x faster. Good. 😃 |
a bit buggy, tho. 4095 versus 4096. Haven't looked at that yet. |
My idea for the goals of (the short-term) v0.1α:
Non-goals:
v1.0:
Releases 0.2 - 1.0 should try to achieve higher performance and move towards the milestone goals.
What should be the performance goals though? C++ is inherently faster than Python so I think we should be able to achieve under 40 ns. Better first whip up a decently fast mock and see how fast it is.
The text was updated successfully, but these errors were encountered: