Honestly speaking, a good way to solve this is not trivial. You would need to: 1. Measure the existing performance on specific data sets. 2. Understand how ma

Honestly speaking, a good way to solve this is not trivial. You would need to: 1. Measure the existing performance on specific data sets. 2. Understand how many of the bottlenecks come from the network latency vs. I/O limits vs. CPU bottlenecks (if using compression). 3. See if any domain-specific compression is needed. 4. Document the typical use cases. Understand why the current solution sucks (e.g. requires redundant user actions). Write down user interaction scenarios. Design the UI to be as efficient as possible for those scenarios. This is a non-trivial amount of work that would require a lot of back-and-forth interaction and on-the-go requirement changes and I don't think it's entirely honest to ask someone to do this work for free in the name of cancer research (after all, you are not donating most of your paycheck to charities, are you?). If the existing solution by IBM sucks, how about making a Request For Proposal [0] and seeing if smaller software vendors could offer something better given that you are actually willing to pay for the work? P.S. A student/hobbyist can probably whip out some sort of a parallel TCP-like thing with a large window for free, but you would get the same performance by just cranking up the TCP window size via sysctl and using multiple HTTP threads (htcat was suggested earlier in the comments). [0] https://en.wikipedia.org/wiki/Request_for_proposal https://en.wikipedia.org/wiki/Request_for_proposal