🚀 go-pugleaf

Well, after some playing around I added a user defined throttle that can be
set and puts a sleep of 20--200 ms within a busy loop.  Also, letting user
define the number of threads--max 100--since I have no idea what kind of
system or bandwidth they will have.  I ran it succesfully at 100
threads--sure, it ran at half speed and eventually got buffer overflows from
my DSL router, but she worked!  Thanks for the input all.  Your commission
checks are in the mail.  There is also good money to be made a well written
thread manual...

ttripp

"Ted Tripp" <ttripp@skypoint.com> wrote in message
news:3e70406f@newsgroups.borland.com...
> Thanks for the info folks.  Yes, it is true I do have plenty of looping.
> This is a desktop (so far) app that does multiple http(Indy 9) reads
> simultaneously.  It seem to rock the first 10-20 seconds then slows
down--I
> can see the CPU avail disappear.  I would have thought the reads on my
> clunky DSL would act as a built in sleep (though, of course we can assume
> the customer may have something better than a clunky DSL).  Anyway, I'll
try
> introducing a few Sleeps within the next few days and see if I can get
some
> performance back.  Oddly, I seem to be having more difficulty simply
getting
> the OnWork Bytes/Sec to work properly, but that's a post for a different
ng.
>
> Another question, I vaguely recall reading that threads are initialized
with
> a certain (default?) amount of memory.  I seem to recall something like
> 1MB--maybe this was a nonwindows OS...  Anyway, if true, can this, should
> this, be tweaked?  If not true, NM.
>
> Again, thanks for all the info...
>
> ttripp
>
>