Closed da3dsoul closed 7 years ago
or make it quicker :-) also server wont benefit from it, only 3rd party that use this (nakamori, and that plex plugin - if he still use this ) Maybe by default we turn this off if it really THAT slow.
There are many slow function.. also I see the glory of your profiler here ;p not sure about all colums but no-time-for-that-right-now 👍
Also we could cut our most lower
or replace startswith
with string[tag.lenght:] ==tag
or something like that. Also there is few parts that I would like to rewrite because I cannot look at that mess in code :-) and maybe then there will be place to use some python-speed-hacks
I mean that c# compiles with faster string operations than Python
yeah, Python ain't the fastest but it not Java also ;-)
You'd be surprised, Java string operations and enumerables are actually pretty fast
It's cleaning up after that it'll have issues with
I'm more than sure that there are some code hacks
we could use to make it quicker. But if you think that Shoko would benefit from this then maybe it should be on server end... cant tell. im not sure, also it would take ages until we would have it there in release
While Im busy at work, I will try to take a look at that profiler you added and start cleaning up and refactoring code
It would take like a day to get released. It's almost done and we're planning a .1
If it's so fast then we can move this part out cazzar would also enjoy it ;-)
On September 6, 2017 3:37:29 PM GMT+02:00, da3dsoul notifications@github.com wrote:
It would take like a day to get released. It's almost done and we're planning a .1
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/bigretromike/nakamori/issues/217#issuecomment-327485474
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
TBH, another major reason is that I am familiar with C# multiprocessing, but not Python....
1.5 million operations should be split up
No problem, it was here because you made it here and it was great why not intercorporate it into bigger app so not only us will benefit it :-) of course only if it won't add bigger delay in the end or if you adding it as a tag cleaning took the there won't be no overhead as now as we lost and clean all records.
On September 6, 2017 3:54:28 PM GMT+02:00, da3dsoul notifications@github.com wrote:
TBH, another major reason is that I am familiar with C# multiprocessing, but not Python....
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/bigretromike/nakamori/issues/217#issuecomment-327490468
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
I ran a profiler, and these are the results. It looks like tag parsing takes the most time. It might be better to move it to server.