-
Notifications
You must be signed in to change notification settings - Fork 8
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
ISSUE | SPEED TESTS | Open discussion #37
Labels
bug
Something isn't working or doesn't seems to work right
discussion
Questions about implementation details, help or support
good first issue
Good for newcomers
help wanted
Extra attention is needed
Comments
Sqllex v0.1.10.4The number of experimental records has been increased from 1,000 to 10,000Running tests/time-tests/main.pyResults for running each function manually# function call # total runtime/(records), speedup .4/.3b
crete_table(db) # 0.00332 sec/(1 table), 1x
insert_fats(db) # 0.21690 sec/(10_000 rec), 3x
insert_slow(db) # 0.92790 sec/(10_000 rec), 3x
insert_many_fast(db) # 0.04220 sec/(10_000 rec), 1.06x
insert_many_slow(db) # 0.04269 sec/(10_000 rec), 1.01x
select_all(db) # 0.03394 sec/(10_000 rec), 1.68x
select_where_1(db) # 0.02888 sec/(10_000 rec), 1.01x
select_where_2(db) # 0.02556 sec/(10_000 rec), 1.5x P.S.: |
0.2.0.0-rc3, SQLite# # total runtime/(records) 0.2.0.0-rc3
# # 0.674s
crete_table(db) # 0.00333 sec/(1 table), 1x
insert_fats(db) # 0.20000 sec/(10_000 rec), 1x
insert_slow(db) # 0.69250 sec/(10_000 rec), 1x
insert_many_fast(db) # 0.03473 sec/(10_000 rec), 1x
insert_many_slow(db) # 0.03330 sec/(10_000 rec), 1.1x
select_all(db) # 0.00995 sec/(10_000 rec), 1.1x
select_where_1(db) # 0.00665 sec/(10_000 rec), 1.1x
select_where_2(db) # 0.00699 sec/(10_000 rec), 1.22x |
Same for v0.2.0.0 |
Speed tests moved to unit tests
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working or doesn't seems to work right
discussion
Questions about implementation details, help or support
good first issue
Good for newcomers
help wanted
Extra attention is needed
Sqllex v0.1.10.3b
Converting
(tuples)
to[lists]
costs for select-like methods 55.8% of all time.This is an results for:
In my opinion it's too much time for such feature. Maybe we should use
numpy.arrays
inside sqllex's processing (instead of lists).Found this example and i think it might be the decision.
https://stackoverflow.com/questions/63409324/why-numpy-array-is-faster-than-list-in-python
P.S.:
<built-in method builtins.isinstance> takes 1/10 of all time
P.P.S:
sqllex v0.1.10.3a
tree/dev/tests/time-tests
The text was updated successfully, but these errors were encountered: