🚀 go-pugleaf

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