CarlosJuncher03 commented on issue #6904: URL: https://github.com/apache/hop/issues/6904#issuecomment-4157814402
I completely agree, and the fact that Hop already has the Execution Information Engine for persistence is a huge advantage. It’s a solid foundation. My suggestion is more about the Developer Experience (DX) during the tuning phase. While external persistence is perfect for auditing, having a quick way to 'read back' and compare the last few runs directly within the GUI would be a game-changer. When we are hunting for bottlenecks or testing small logic adjustments, switching to an external SQL editor or Grafana to check if we gained 5 or 10 seconds breaks the development flow. If the GUI could leverage that existing persisted data to show a simple 'Current vs. Previous' delta, it would turn Hop into an even more powerful IDE for performance optimization. It’s less about storing the data and more about making it actionable for the developer in real-time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
