You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/01/07 15:52:49 UTC

[GitHub] [couchdb] ksnavely edited a comment on issue #2360: Make the rexi:stream2 interface unacked message limit configurable

ksnavely edited a comment on issue #2360: Make the rexi:stream2 interface unacked message limit configurable
URL: https://github.com/apache/couchdb/pull/2360#issuecomment-571333719
 
 
   Alright, @wenli200133 ran some partitioned query benchmarks for this recently, here is what she found:
   
   
   q | stream_limit | mean rows | std-dev % | ratio | 3 std-dev %
   -- | -- | -- | -- | -- | --
   1 | 5 | 519961.67 | 0.48 |   |  
   1 | 10 | 519948 | 0.82 | 0.999974 | 2.8504736
   1 | 100 | 385213.67 | 30.3 | 0.74087 | 90.933281
   1 | 1000 | 388600.33 | 28 | 1.008792 | 123.76918
   8 | 5 | 2739565.67 | 0.23 |   |  
   8 | 10 | 2750676.33 | 1.01 | 1.004056 | 3.1075714
   8 | 100 | 2753663.67 | 0.21 | 1.001086 | 3.0948021
   8 | 1000 | 2763239.67 | 0.55 | 1.003478 | 1.7661823
   
   For higher Q values, there was no statistically significant variation in performance with the stream limit. Note the large instability at 100 and 1000 for q=1. Again this was for 1000 keys queried using startkey and limit.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services