On 04/12/2019 02:23, Behrang Saeedzadeh wrote:
> I am not expecting it to take less time, but to provide better throughput.
Despite what you appear to think, you have written two synchronous,
blocking I/O upload servlets. Not one synchronous and one
non-synchronous. With synchronous I/O less time
I am not expecting it to take less time, but to provide better throughput.
With 1000 concurrent users, the sync version was still performing better
(mean req/second).
Best regards,
Behrang Saeedzadeh
(Sent from my cellphone.)
On Mon, 2 Dec. 2019, 8:44 am Mark Thomas, wrote:
> On 01/12/2019
On 01/12/2019 02:17, Behrang Saeedzadeh wrote:
> Any ideas what am I missing here?
Async provides scalability, not raw performance.
You haven't written a async file upload servlet. That would require
non-blocking I/O and look more like this:
Source code with Gatling tests here (WIP):
https://github.com/turingg/file-server
I wanted to compare the performance/throughput of an async file upload
servlet to a sync version. To do that, I intentionally configured Tomcat to:
* Use at most 2 HTTP connector threads
* Accept up to 1000
