-
Notifications
You must be signed in to change notification settings - Fork 111
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
Qulice release 0.16.4 is too slow #767
Comments
@davvd valid bug |
@HDouss thanks for the report, I topped your acc for 15 mins, payment ID |
@krzyk @HDouss yes, the reason is here: https://github.com/teamed/qulice/pull/735/files#diff-2cf0472dd4aa25abe70bb2e0426ea000R154 |
@davvd this is urgent |
@dskalenko this task is yours, please help (see our key principles of work). If you have any technical questions, don't hesitate to ask right here; The budget here is 30 mins, which is exactly how much time will be paid for, when the task is completed |
@dskalenko It will be simple to verify. Now we bootstrap Checkstyle from
scratch for every file under check. After fix we should initialise
Checkstyle once per analysis.
|
@mkordas ok I see, thanks, I just thought about some test ... :) |
@dskalenko unfortunately we don't have environment for running perf tests...
|
@dskalenko Thanks ! |
@dskalenko done, I added 30 mins in payment added +30 to your rating, now it is equal to +60 |
@davvd this is not urgent |
Using qulice for some time, I realized that 0.16.4 release is much slower than the older ones. I tried to integrate qulice checking in a simple (rather small) project with 3 sub modules. The table below compares the maven build time when:
Every figure in this table is a mean build time of 3 builds. Even if these figures are not necessarily significant, it is obvious that 0.16.4 version has a performance issue (as I said before this was noticed in many other projects). I expect to figure out which new feature or which bug resolution has introduced this performance issue and to resolve it.
The text was updated successfully, but these errors were encountered: