If cache key creation makes memoization, on average, more expensive than just running a function call, it's not worth doing. We need to create a suite of tests to measure medium-scale runtime with and without memoization.
Description
Description
Details
Details
Related Changes in GitLab:
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Add very basic benchmark comparison script. | repos/abstract-wiki/wikifunctions-usage-analytics!2 | apine | apine-benchmark | main | |
| Add benchmarking code. | repos/abstract-wiki/wikifunctions-usage-analytics!1 | apine | apine-benchmark | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | cmassaro | T430696 [Hypothesis] DE2.1.2 Faster NLG: Gotta Go Fast, Epically Fast | |||
| Resolved | cmassaro | T433272 Memoize Function Calls and Sub-Calls | |||
| Resolved | ecarg | T436125 Memoize a small set of functions | |||
| Resolved | cmassaro | T436268 Benchmark function calls with/without memoization |
Event Timeline
Comment Actions
apine opened https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions-usage-analytics/-/merge_requests/1
Add benchmarking code.
Comment Actions
apine merged https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions-usage-analytics/-/merge_requests/1
Add benchmarking code.
Comment Actions
apine opened https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions-usage-analytics/-/merge_requests/2
Add very basic benchmark comparison script.
Comment Actions
apine merged https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions-usage-analytics/-/merge_requests/2
Add very basic benchmark comparison script.
Comment Actions
We still need to actually run this code, but the scripts are ready for basic benchmarking.
Do we want this to be more elaborate, with graphs/visualizations?