From pmix at hendrie.id.au  Tue Feb  4 04:23:25 2020
From: pmix at hendrie.id.au (Michael Hendrie)
Date: Tue, 4 Feb 2020 14:53:25 +1030
Subject: Issue with high request rate tests
Message-ID: <2C5EEEA1-9D88-46F6-90BE-8BE3FAB2FA20@hendrie.id.au>

Hi,

I have web-polygraph 4.12.0 installed and running well but have just increased capacity of the test set and now receive an error "integer overflow as a result of `int' (|2.23949e+09| > 2147483647)" when I try to run tests above 23000 req/sec.

I have attached a config file for reference.

Any suggestions on how to overcome this so I can run higher request rate tests?

Thanks,

Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: polymix-4_custom.pg
Type: application/octet-stream
Size: 6023 bytes
Desc: not available
URL: <http://lists.web-polygraph.org/pipermail/users/attachments/20200204/fd1c7c22/attachment-0001.obj>

From rousskov at measurement-factory.com  Tue Feb  4 13:54:19 2020
From: rousskov at measurement-factory.com (Alex Rousskov)
Date: Tue, 4 Feb 2020 08:54:19 -0500
Subject: Issue with high request rate tests
In-Reply-To: <2C5EEEA1-9D88-46F6-90BE-8BE3FAB2FA20@hendrie.id.au>
References: <2C5EEEA1-9D88-46F6-90BE-8BE3FAB2FA20@hendrie.id.au>
Message-ID: <f8c22c93-dafd-57e4-ce48-cea117ebce6a@measurement-factory.com>

On 2/3/20 11:23 PM, Michael Hendrie wrote:

> I have web-polygraph 4.12.0 installed and running well but have just increased capacity of the test set and now receive an error "integer overflow as a result of `int' (|2.23949e+09| > 2147483647)" when I try to run tests above 23000 req/sec.
> 
> I have attached a config file for reference.

AFAICT, initialization of the "wsc" PGL variable on line 142 overflows
with your workload parameters. You can work around that specific problem
by converting to integer _after_ the division, when calling the
working_set_cap() function:

  float wsc = peak_fill_rate * platDur; // number of objects in the WS
  working_set_cap(int(wsc / clientHostCount));

Long-term, we should switch PGL to 64-bit integers, of course. Most of
the runtime Polygraph code uses them as needed already.


HTH,

Alex.

From pmix at hendrie.id.au  Tue Feb  4 23:10:11 2020
From: pmix at hendrie.id.au (Michael Hendrie)
Date: Wed, 5 Feb 2020 09:40:11 +1030
Subject: Issue with high request rate tests
In-Reply-To: <f8c22c93-dafd-57e4-ce48-cea117ebce6a@measurement-factory.com>
References: <2C5EEEA1-9D88-46F6-90BE-8BE3FAB2FA20@hendrie.id.au>
 <f8c22c93-dafd-57e4-ce48-cea117ebce6a@measurement-factory.com>
Message-ID: <029FEF36-FFC3-446E-A799-F24F5E5079D6@hendrie.id.au>


> On 5 Feb 2020, at 12:24 am, Alex Rousskov <rousskov at measurement-factory.com> wrote:
> 
> AFAICT, initialization of the "wsc" PGL variable on line 142 overflows
> with your workload parameters. You can work around that specific problem
> by converting to integer _after_ the division, when calling the
> working_set_cap() function:
> 
>  float wsc = peak_fill_rate * platDur; // number of objects in the WS
>  working_set_cap(int(wsc / clientHostCount));

Thanks, that allows the test to run up to the limit of my environment (40,000 req/sec)

Michael