🚀 go-pugleaf

Runs so fast for me on XP that the button barely goes down.

Max Bolingbroke

"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
>
>
>
>
>

"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!)?

Are you doing your timing in the IDE or in a compiled exe?

"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!

"Max Bolingbroke" <batterseapower{no@spam}hotmail.com> wrote in message
news:a6k7sr$djn$1@newsfeed.th.ifl.net...
> Runs so fast for me on XP that the button barely goes down.

Thanx, that was encouraging! ;-)

Anyway, point being, there **IS** a huge difference between performance on
this code on WinNT 4.0 and almost any other windows system. We have a test
department at our company with plenty of testing mashines and different
environments, and our customers have up to thousands of computers, making
room for chance in these test next to nothing. There is really no reason
everyone to post their results (and with the results from those who've done
it, I think one should get the picture already).

My big consern is if anyone has either a good *explaination* or any
*solution*.

Best regards
 -Anders

> "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
> >
> >
> >
> >
> >
>
>

My timing has been on the compiled EXE, but I have the feeling the same
result occur in the IDE.

-Anders

"George Copeland" <tma1_99@usa.net> wrote in message
news:qGmj8.10839$RK1.2485655611@newssvr11.news.prodigy.com...
> "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!)?
>
> Are you doing your timing in the IDE or in a compiled exe?
>
>

"Anders P" <ap@comp.nospan> wrote in message
news:DlCj8.3652$Mg4.3938@news1.bredband.com...

> Anyway, point being, there **IS** a huge difference between performance on
> this code on WinNT 4.0 and almost any other windows system. We have a test
> department at our company with plenty of testing mashines and different
> environments, and our customers have up to thousands of computers, making
> room for chance in these test next to nothing. There is really no reason
> everyone to post their results (and with the results from those who've
done
> it, I think one should get the picture already).
>
> My big consern is if anyone has either a good *explaination* or any
> *solution*.

I would say that you have everything you need for a call to MS support.  Let
us know what they say.

"George Copeland" <tma1_99@usa.net> wrote in message <news:33Kj8.65638$em3.2360799327@newssvr30.news.prodigy.com>...

> "Anders P" <ap@comp.nospan> wrote in message
> news:DlCj8.3652$Mg4.3938@news1.bredband.com...

> > My big consern is if anyone has either a good *explaination* or any
> > *solution*.
>
> I would say that you have everything you need for a call to MS support.  Let
> us know what they say.

"This behavior is by design" and "What is your credit card number"?

--
Joe Foster <mailto:jlfoster%40znet.com>     Got Thetans? <http://www.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!

LOL :)

"Joe "Nuke Me Xemu" Foster" <joe@bftsi0.UUCP> wrote in message
news:u8v76ummnhc311@corp.supernews.com...

> > I would say that you have everything you need for a call to MS support.
Let
> > us know what they say.
>
> "This behavior is by design" and "What is your credit card number"?

Sorry, you are full of crap.  I have called MS developer support on numerous
occasions.  They have spent hours on the phone with me researching my
issues, and when it turned out they couldn't help me or that it really was
their bug, they didn't charge me a dime.  I'm sure you can imagine why they
might charge to write someone's application for them.

> > My big consern is if anyone has either a good *explaination* or any
> > *solution*.
>
> I would say that you have everything you need for a call to MS support.
Let
> us know what they say.

Well, as I am working in a Microsoft Certified Partner company, I actually
*WILL* call call MS support line. However, history shows that newsgroups
just as often provide just as fast, just as relieable answers. I will keep
you guys informed of any intelligible feedback ;-)

-Anders

Well, as it turned out, Microsoft no long supports Windows NT 4.0. So much
for any help from that direction. Apparently, they supprt only the two last
versions (that would be Win2K and XP).

The guys at MS also said that som much was being turned upside down and
inside out with memory handling and allocation from NT4.0 to the next
platforms that it would impossible to make any sense of it any longer. We'll
just have to conclude that WinNT suxx!!

-AP



"Anders P" <ap@comp.nospan> wrote in message
news:nNPj8.270$mq4.151@news2.bredband.com...
> > > My big consern is if anyone has either a good *explaination* or any
> > > *solution*.
> >
> > I would say that you have everything you need for a call to MS support.
> Let
> > us know what they say.
>
> Well, as I am working in a Microsoft Certified Partner company, I actually
> *WILL* call call MS support line. However, history shows that newsgroups
> just as often provide just as fast, just as relieable answers. I will keep
> you guys informed of any intelligible feedback ;-)
>
> -Anders
>
>

"AP" <a@b.com> wrote in message <news:a7f3mc$pk3$1@lise.netcom.no>...

> Well, as it turned out, Microsoft no long supports Windows NT 4.0. So much
> for any help from that direction. Apparently, they supprt only the two last
> versions (that would be Win2K and XP).

However, I'm sure they'd look into it if you answered the question,
"What is your credit card number"...

> The guys at MS also said that som much was being turned upside down and
> inside out with memory handling and allocation from NT4.0 to the next
> platforms that it would impossible to make any sense of it any longer. We'll
> just have to conclude that WinNT suxx!!

In other words, "This behavior is by design"?  Is memory management
faster on Lose2K Pro and/or LoseXP Pro, both of which use what used
to be the LoseNT kernel?

--
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!

"AP" <a@b.com> wrote in message <news:a7f3mc$pk3$1@lise.netcom.no>...

> Well, as it turned out, Microsoft no long supports Windows NT 4.0. So much
> for any help from that direction. Apparently, they supprt only the two last
> versions (that would be Win2K and XP).

Has somebody at Micro$haft been telling lies yet again?  LoseNT
4.0 isn't scheduled to enter "GFY phase" until 30 June 2003:

 URL:http://microsoft.com/windows/lifecycle.asp

--
Joe Foster <mailto:jlfoster%40znet.com>     Got Thetans? <http://www.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!