-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Measure performance of gensim 4.0.0 vs previous versions #2887
Comments
This link is also broken for me – I get 400. @mpenkov this way of creating tickets seems more trouble than worth, with the context missing. |
I'll take it up with github support. It's convenient, but only when it works. |
@piskvorky From github support:
I'll keep my eyes open for the problem in case it recurs. |
Some Word2vec measurements here: #2939 (comment) I wonder what the original "Not every 1-line decision; just ones that are in inner loops of hot-spot code." was referring to though, the link is still broken. Probably some change of code deep in C loops. |
Comparing current fasttext 3.8.3training on a 124301826 raw words (88163974 effective words) took 107.3s, 821794 effective words/s fasttext developtraining on a 124301826 raw words (88166519 effective words) took 96.4s, 914282 effective words/s word2vec 3.8.3training on a 124301826 raw words (88162276 effective words) took 52.3s, 1684982 effective words/s word2vec developtraining on a 124301826 raw words (88166114 effective words) took 50.0s, 1762436 effective words/s phrases 3.8.3using 17692319 counts as vocab in Phrases<0 vocab, min_count=5, threshold=10.0, max_vocab_size=40000000> phrases developmerged Phrases<17692319 vocab, min_count=5, threshold=10.0, max_vocab_size=40000000> CC @gojomo FYI. I also double-checked loading models with |
Not every 1-line decision; just ones that are in inner loops of hot-spot code.
Definitely a big TODO: compare performance before/after.
Originally posted by @piskvorky in https://github.com/_render_node/MDExOlB1bGxSZXF1ZXN0MzQ5Mjk1NTk1/timeline/more_items
The text was updated successfully, but these errors were encountered: