Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

cubed-dev / cubed Public

Notifications You must be signed in to change notification settings
Fork 14
Star 136

Code
Issues 85
Pull requests 11
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Measure peak memory before and after calling remote function#52

Merged

tomwhite merged 4 commits intomaincubed-dev/cubed:mainfrom mem-statscubed-dev/cubed:mem-statsCopy head branch name to clipboard

Jul 13, 2022

+99-8

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Jul 13, 2022

Record peak mem before and after running func
tomwhite
committed
Record event history in CSV files at end of computation
tomwhite
committed
Change Lithops example to record event history
tomwhite
committed
Add examples/lithops-matmul-random.py
tomwhite
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.