-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
With the changes for #58 I think we are on the right track but to be fair we need to understand why our competitor is getting that many connection errors: having such errors can increase spring RSS and affect throughout and depending why they got them it could make their results less valid.
If they have connection errors because:
- our default timeout values for the load generator are too punitive
- our measurements start too early whilst they are starting up
We need to fix our benchmarks - or at least, try hard.
If the connection errors, instead, are due to internal spring mechanisms which, under load, drop connections due to internal timeout, it's fine (I am open to discuss it) to report it and once this will be open up to the community it is them which should fix it instead.
Metadata
Metadata
Assignees
Labels
No labels