precision_at_k is slower than training
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 724
- PR merge metrics
- No merged PRs in 30d
Description
How come evaluation, precision_at_k, is so slow? On the training set, it takes 2.5 minutes per epoch but the test set at 10% the size has taken at least 10 minutes and there's no way to tell how much longer it'll take. Anyone else have this issue?
`test_precision = precision_at_k(model, test_matrix, k=12, train_interactions=train_matrix).mean()`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the precision_at_k(model, test_matrix, k=12, train_interactions=train_matrix) call and trace the evaluation implementation it invokes; no source file or test is named in the report. Reproduce the timing difference on training and test matrices, then use the observed behavior to define the needed performance fix and a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100