CLI UI report not in sync

[gserra-olx]

1M requests were already completed according to the cloudwatch logs
but this is the status of the UI in the meantime...

 53.3%
[###########################                         ]

Region: ap-northeast-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     53803     2.2 GB     0.440s       26.59     1.1 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    7.526s     0.074s          0          0

Region: ap-northeast-2
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     49446     2.0 GB     0.482s       22.59     920 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    7.486s     0.074s          0          0

Region: ap-southeast-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     61952     2.5 GB     0.382s       30.20     1.2 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.485s     0.075s          0          0

Region: ap-southeast-2
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     53469     2.2 GB     0.445s       24.91     1.0 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.456s     0.075s          0          3

Region: eu-central-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     49759     2.0 GB     0.472s       23.65     963 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    7.536s     0.076s          0          2

Region: eu-west-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     55144     2.2 GB     0.422s       25.73     1.0 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.456s     0.074s          0          4

Region: sa-east-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     48010     2.0 GB     0.492s       22.07     899 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.389s     0.076s          0          1

Region: us-east-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     52928     2.2 GB     0.449s       24.07     980 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.490s     0.075s          0          2

Region: us-west-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     51611     2.1 GB     0.456s       24.52     998 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    8.427s     0.029s          0          3

Region: us-west-2
   TotReqs   TotBytes    AvgTime    AvgReq/s  (post)unzip
     56785     2.3 GB     0.415s       26.99     1.1 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    7.509s     0.076s          0          1

[gserra-olx]

p.s. would be nice to know which AWS region it is using for the SQS... I assume that sorting alphabetically it goes by default to the one in the first position of the list... ap-northeast-1 (Tokyo) I assume

[gserra-olx]

there... seems to go by default to us-east-1 which is suboptimal for me... we shall have it parametrized ..... ahhhh.. it took the one on top of the [regions] list in the INI (we shall document that in the template)

[cwaltken-edrans]

So to solve this we document this in the default ini template?

[akhilesharora]

How do we exactly know which region is it running the test? Because by default it was pointing to us-east-1 everytime since all the AWS Lambda logs are getting generated in the us-east-1 .

[zeph]

@cwaltken-edrans partially... we need to document that the first active/uncommented region in the list is going to be the one holding the SQS. And we need to fix the performance of the metrics aggregation and reporting... it can't fall 10min behind.

[zeph]

@akhilesharora each AWS Lambda generates logs in its region. It runs in the regions u configure

[cwaltken-edrans]

We should still investigate if we can improve upon this.