🚀 go-pugleaf

"Anders P" <ap@comp.nospan> wrote in message <news:xIfj8.3172$Mg4.3426@news1.bredband.com>...

> I have this performance issue with NT 4.0 for my Visual Basic app. I have
> isolated the problem into the process of adding many items to a collection.
> The same code and EXE-file runs REMARKABLY slower on Win NT 4.0 than on e.g.
> Win2000 or Win98.  Typical number would be 10-50 times slower on NT with
> same hardware. Anyone having clues to the reason and any workarounds (when
> upgrading the NT systems is out of the question!)?
>
> best regards
>  -Anders
>
> Test the follwing code for youself (paste code in a form with command button
> and label):
>
> Private Sub Command1_Click()
> Dim dtStart     As Date
> Dim dtStop      As Date
> Dim collTest    As Collection
> Dim i           As Long
>   Set collTest = New Collection
>   dtStart = Now
>   For i = 1 To 100000
>     collTest.Add "qwrqweltjqwegkwldjgsldkjsldqwertyjf"
>   Next i
>   dtStop = Now
>   Label1.Caption = DateDiff("s", dtStart, dtStop)
> End Sub

I think you will find that it is even worse than you think.
Test how long it takes to do "Set collTest = Nothing" too!

Have a look at this:

 URL:http://groups.google.com/groups?selm=u2cjn68927u2a8%40corp.supernews.com

The "Pooled" class can be pretty much anything that will
tolerate not being cleaned up promptly.

--
Joe Foster <mailto:jlfoster%40znet.com>  Wanna buy a Bridge? <http://xenu.net/>
WARNING: I cannot be held responsible for the above        They're   coming  to
because  my cats have  apparently  learned to type.        take me away, ha ha!