You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hop.apache.org by "mattcasters (via GitHub)" <gi...@apache.org> on 2026/09/29 13:57:37 UTC

Re: [I] [Task]: Create a Hop sizing guide (hop)

mattcasters commented on issue #2408:
URL: https://github.com/apache/hop/issues/2408#issuecomment-5891785036

   Sizing advice for tiny devices for edge-node computing.  Try a very simple pipeline that reads a JSON file and writes it to a REST web service somewhere. Throw out all plugins we don't need. What would be the memory and disk requirements?
   
   Sizing advice for a typical data engineer?  Concerns are Memory, CPU cores, Disk space,  Network performance to databases, display Full HD.
   
   Sizing advice for big data use-cases?  Delegated to Spark?
   


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org