CarlosJuncher03 opened a new issue, #7991: URL: https://github.com/apache/hop/issues/7991
### What would you like to happen? When developing or testing pipelines that process large volumes of data, the pipeline execution can consume enough CPU or memory to make Hop GUI slow or temporarily unresponsive. This affects the development experience because the user may lose the ability to monitor metrics, inspect data, review logs, or stop the execution safely. A common workaround is to configure a separate Hop Server and use the Remote Pipeline Engine. Although this protects the Hop GUI process, it requires the user to install, configure, start, and maintain a separate runtime. It also makes the development and data-inspection experience less direct than local execution. It would be valuable to have an optional isolated execution mode managed directly by Hop GUI. From the user’s perspective, Hop could prepare an isolated runtime when the pipeline starts, execute the pipeline outside the Hop GUI process, and continue presenting logs, metrics, execution status, and bounded data samples through the existing interface. The isolated runtime could also support configurable resource boundaries, such as maximum memory, CPU usage, concurrent executions, and an idle timeout. The specific implementation—separate JVM, container, or another mechanism—could remain open for discussion by the community. This capability would: Keep Hop GUI responsive during heavy executions. Protect the development environment from pipelines with excessive resource consumption. Reduce the operational work required to configure a separate Hop Server only for development. Preserve a consistent experience for running, monitoring, stopping, and inspecting pipelines. Provide an intermediate option between local in-process execution and a manually managed remote cluster. The intention is not to replace Hop Server or distributed execution engines, but to make isolated execution more accessible for development and testing directly from Hop GUI. ### Issue Priority Priority: 3 ### Issue Component Component: Infrastructure -- 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]
