Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
/ one-sdk-benchmark Public archive

Comparing memory usage of OneSDK between v1 and v2

Notifications You must be signed in to change notification settings

jnv/one-sdk-benchmark

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OneSDK Memory usage in v1 vs. v2

Memory usage measurement of @superfaceai/one-sdk. This is intended to roughly measure base heap usage of OneSDK between versions using Clinic.js Doctor.

Usage

Run npm start or manually execute the scripts:

  1. ./setup.sh to install individual dependencies and install clinic package (via npx)

  2. ./single-profile.sh to run the benchmark; this will run single-profile.js in v1 and v2 directory

    • each script is executed twice: first time to warm up a cache, second time with clinic doctor for profiling and a heap size limited to 128 MB
    • after each profiling an interactive profile snapshot is generated and opened by the default browser

Contents

  • single-profile.js measures OneSDK with single profile and map fetched from the registry, currently weather/current-city with wttr-in provider is used

About

Comparing memory usage of OneSDK between v1 and v2

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published