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
Launching node components takes more than 5 seconds. Same behavior can be encountered on the researcher notebook while importing classes such as Experiment or request for the first time.
After investing the performance using python profiler, I've realized that it is due to time that is consumed during the module imports. For example, importing modules in node/cli.py module takes almost 5s each time node CLI is called. Since fedbiomed_run executes node.cli at least two times (one for configuration generation second for launching the node ), starting a node almost take 8-9 seconds.
Please see result for the import section in fedbiomed.node.cli:
After the first inspection, I realized it is probably due to environ object that is imported almost every module in Fed-BioMed. This can be a bug or an implementation choice depending on the reason behind the time consumed. However, it needs to be investigated and clarified.
The text was updated successfully, but these errors were encountered:
srcansiz
added
the
candidate
an individual developer submits a work request to the team (extension proposal, bug, other request)
label
Sep 5, 2023
Launching node components takes more than 5 seconds. Same behavior can be encountered on the researcher notebook while importing classes such as
Experiment
orrequest
for the first time.After investing the performance using python profiler, I've realized that it is due to time that is consumed during the module imports. For example, importing modules in
node/cli.py
module takes almost 5s each time node CLI is called. Sincefedbiomed_run
executesnode.cli
at least two times (one for configuration generation second for launching the node ), starting a node almost take 8-9 seconds.Please see result for the import section in
![image](https://private-user-images.githubusercontent.com/28705816/265719683-54ecffdc-7ddf-4715-9a1e-17ca6ed93e0c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI0NTE0NDksIm5iZiI6MTcyMjQ1MTE0OSwicGF0aCI6Ii8yODcwNTgxNi8yNjU3MTk2ODMtNTRlY2ZmZGMtN2RkZi00NzE1LTlhMWUtMTdjYTZlZDkzZTBjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzMxVDE4MzkwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFjNzJiOWQwOGVlN2U5NDJmZjk3N2U5OGIzMTMwMDNjMDEwNjIyNTkzMjQ4ZDc3ODMxNzcwODdiZDZkODU3YjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.cq20aAgsv7S22sks4A-ANZ1CGXg6qwBN5bFMO39fQjg)
fedbiomed.node.cli
:After the first inspection, I realized it is probably due to
environ
object that is imported almost every module in Fed-BioMed. This can be a bug or an implementation choice depending on the reason behind the time consumed. However, it needs to be investigated and clarified.The text was updated successfully, but these errors were encountered: