Hi Arno,

Not sure how the debug GUI exe works but I found a solution for the service:

In ...WndControl.pas,

  TIcsWndControlVersion  = 110;
  CopyRight : String     = ' TIcsWndControl (c) 2002-2008 F. Piette V1.10 ';

  WH_MAX_MSG                   = 400; <== MODIFIED THIS from 100

so that it would create less windows per same number of messages. With this
change, My also ICS stress tester can open > 15k connections concurrently.
In a real life case, since there will not be a stress tester on the same
machine, I think it is ok. This must be a non-paged RAM drought issue...

Could you make WH_MAX_MSG a property so that each time users update ICS,
they would not need to change ICS source?



On Thu, May 20, 2010 at 9:46 PM, Arno Garrels <arno.garr...@gmx.de> wrote:

> Fastream Technologies wrote:
> > Yes I see but under the same computer, same Win7Pro, same 4GB RAM,
> > the GUI -debug- project that does exactly the same thing works very
> > well!!
> I guess both use the same ICS, isn't it?
> So most likely something in your service-code makes the difference.
> --
> Arno Garrels
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to