futureverse / futureverse/future

BENCHMARKING: Record timing and memory stats for the various steps in futures

Open
#59 5 comments 0 reactions 0 assignees View on GitHub
enhancement feature request feature/profiling
Dominant language
R
Stars
1k
Forks
92
PR merge metrics
No merged PRs in 30d

Description

Record timing and memory stats for the various steps in futures, e.g. creation, identification of global variables, exporting globals, launching future, time for future to complete, collection of value/exceptions etc. This should be done (optional?) for all types of futures.

Contributor guide

Open the contributing guide

Research direction

Start by mapping the future lifecycle steps named in the issue: creation, global-variable identification and export, launch, completion, and value or exception collection. Compare how these steps apply across the different future types, then define optional timing and memory statistics and verify that they can be recorded for each type.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
distributed-systems, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.