Proposal: Improve general performance

[wickenico]

ℹ️ Initiative from #173.

About performance improvements:

• There are still many items that can be cached

  • Currently only brew info is cached
  • brew list --cask, brew list --formula --versions, brew leaves, etc. can also be cached

• brew update, brew outdated caching

  • This requires discussion on caching strategy
  • e.g., Only fetch if cache data is older than 15 minutes, otherwise use cache. Or don't cache at all

• Call logic optimization

  • There are still duplicate calls and sequential executions that could be optimized
  • Also, rendering as each call completes could improve user experience (I haven't checked the code, but it seems like everything renders at once after all queries finish)

• Call latency

  • The "too slow" issue in Toooo Sloooow! #157 might be related to brew command call latency
  • I also experienced call latency while working on this PR, which prevented me from doing a more accurate analysis (this is why I mistakenly thought brew formulae was slow)
  • I haven't identified the root cause yet

• ...

[moseoh]

Hi @wickenico,

To tackle the points mentioned in this issue more systematically, I've organized them into a task list. Would you like me to proceed with these, or would you prefer me to open separate sub-issues for each?

• Cache Homebrew Metadata: Implement caching for brew list --cask, brew info, etc
• Cache Update/Outdated Status: Add caching for brew update/outdated (15-min default, with configurable intervals).
• Optimize Call Logic: Refactor redundant methods and streamline call flows (including potential frontend changes).
• Analyze Call Latency: Investigate the root cause of the current latency and implement fixes.

[wickenico]

@moseoh Would be totally fine to have just this issue for all of them. So every item is packed in its own PR to avoid conflicts. Let's get it on thank you 🚀

[satwikShresth]

can I suggest using api (docs) directly instead of using the cli