-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
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
Overloading __getattribute__ in Transcript causes a massive slowdown #154
Comments
lucventurini
added a commit
that referenced
this issue
Mar 13, 2019
…now Mikado compare can be used with parallelism
lucventurini
added a commit
that referenced
this issue
Mar 22, 2019
…xternal.score (#154) from Transcript objects WITHOUT slowing down the whole application.
lucventurini
added a commit
that referenced
this issue
Mar 22, 2019
lucventurini
added a commit
that referenced
this issue
Mar 22, 2019
Fixed, tested by @gemygk. Closing. |
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
…or external metrics; now Mikado compare can be used with parallelism
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
…xternal.score (EI-CoreBioinformatics#154) from Transcript objects WITHOUT slowing down the whole application.
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After testing, I realised that overloading the getattribute method causes a massive slowdown in basically the whole program. This is because the Transcript class is practically ever-present, and overloading the base method causes a massive slowdown in everything, from the comparison, to the statistics, to any core functionality. I am now testing whether removing the overloading causes problems with the external attributes (the original problem for which the overloading was introduced) and if so, what are the possible solutions.
The text was updated successfully, but these errors were encountered: