On Mon, 25 Jun 2001, Mark Pace Balzan wrote:
> I am very well aware that the recommended o/s for Polygraph is
> Unix, but I am trying to set it up on Windows 2000 using the
> binaries on thw web polygraph site.
>
> My problem is as follows:
> When I try to run polysrv.exe --config workloads/polymix-3.pg or polyclt
> with the same parameters, I get no console output and the memory usage
> increases tremendously until the machine runs out of memory.
In general, PGL parser memory usage depends on the request rate you
set in polymix-3.pg or a similar workload file. For high request rates
(e.g., 4000 req/sec), you will need 256MB of RAM for Unix and probably
more for MS Windows.
However, I think the problems you experience cannot be explained by
normal PGL memory consumption. I am able to reproduce your problem on
our W2K machine. We will try to find the cause and improve memory
usage on W2K.
> I have tried to setup simple.pg and this was immediately sucessful
> with no problems for both client and server
That's a good sign.
> I have also tried polymix2. While the server runs ok, the client
> starts but then fails as below.
> ...
> 000.12| PolyApp.cc:128: error: 1/1 (s10022) An invalid argument was supplied.
Yuck. Another MS select(2) incompatibility! The patch is attached.
With the patch applied (and Polygraph recompiled from scratch), I am
able to start a PolyMix-2 test.
Thanks,
Alex.
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:19 MDT