[WEB][DRAFT][42108] Loose Ideas
birdyblood opened this issue · 0 comments
These ideas have not been retain by the team 42108 but we want to track them :
Waste Loop
Description
Detect calculation loop which create some useless calculation but the result never read
Feeling
Difficult to implement or detect
Filter Collection Without Streaming
Description
Sometimes we compute a large collection to finally retain one element. Useless calculation
Feeling
Difficult to implement or detect
Unused Library
Description
Sometimes a lot of libs are declared in pom , gradle or other tool but not used in the code. CI/CD download always these libs but never used.
##Feeling
how to detect ??
Docker Layer
Description
Detect in the docker file multiple layer to reduce layer impact
Feeling
how to do
Unit Test assert true = true
Description
Detect useless unit test to avoid useless computation
Feeling
easy to detect assert true = true but other case ?
SQL Update with where instead of multiple update
Description
Detect loop with SQL update
Feeling
perhaps?
Conf Spring HTTP
Description
Parse config spring yaml, xml or properties to propose to activate http2 and compression to reduce data on the network
Feeling
seems to be implementable
Memory Leak
Description
Detect ressource not closed
Feeling
Read file with stream instead of load everything
Description
Not load all the file but use a stream to open file
Feeling
Force use of Spring WebFlux
Description
Detect API not using webflux , webflux use reactive programming which can improve performance and so avoid energy resource.