We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing the Network class takes quite some amount of time depending on the platform and hardware. Below are some examples:
Network
[email protected]/4.80GHz
M1 [email protected]/3.2GHz
[email protected]
3.12.3
3.12.4
Python 3.12.4
I used the following commands for the measurement:
time python -c 'from mytoolit.can import Network'
Measure-Command { python -c 'from mytoolit.can import Network' }
repeated each measurement four times and calculated the average time.
The text was updated successfully, but these errors were encountered:
Looks like the biggest contributor (56.2 %) to the slow import time is the tables library. At least that is what I gathered after executing:
tables
python3 -X importtime -c "from mytoolit.can import Network" 2> read.prof
and checking the result with Tuna:
on the Linux NUC.
Sorry, something went wrong.
No branches or pull requests
Description
Importing the
Network
class takes quite some amount of time depending on the platform and hardware. Below are some examples:[email protected]/4.80GHz
M1 [email protected]/3.2GHz
[email protected]
3.12.3
3.12.4
Python 3.12.4
I used the following commands for the measurement:
time python -c 'from mytoolit.can import Network'
Measure-Command { python -c 'from mytoolit.can import Network' }
repeated each measurement four times and calculated the average time.
The text was updated successfully, but these errors were encountered: