Micro optimizations

[lippserd]

No description provided.

[julianbrost]

@lippserd What's the future plan for this PR?

[lippserd]

@lippserd What's the future plan for this PR?

Honestly, I don't know yet but I asked @Al2Klimov to test whether this PR does anything in terms of performance, cpu and memory usage.

[Al2Klimov]

TODO

• throw away everything not to be merged anyway (e.g. exit after config sync)
• make CI/CD happy

[Al2Klimov]

Tip: git push -f commit by commit sleeping 10s inbetween, so we see whose commits broke the CI/CD.

[lippserd]

Tip: git push -f commit by commit sleeping 10s inbetween, so we see whose commits broke the CI/CD.

The new types from your commits don’t have the database interfaces implemented and thus the delete fails if I remember correctly.

[oxzi]

In order to cleanup relicts, I came across this PR. After skimming the changes, I found nothing to categorize as very important. Furthermore, nothing merges anymore and some code went to the IGL.

Would you like to rebase or recreate some parts of this or would you prefer closing this issue, @lippserd?

[lippserd]

In order to cleanup relicts, I came across this PR. After skimming the changes, I found nothing to categorize as very important. Furthermore, nothing merges anymore and some code went to the IGL.

Would you like to rebase or recreate some parts of this or would you prefer closing this issue, @lippserd?

I will close it. A performance analysis regarding using a different JSON lib and timestamp and checksum refactoring might be interesting, but that's something for when we run out of tasks 😆.

[julianbrost]

using a different JSON lib

encoding/json/v2? 👀 (Would probably make sense to see what happens within the Go standard library before evaluating external libraries.)