Re: Performance issue after coverting from Framework 1.1 to 2.0

Hi,

I think that I encountered the same problem: A large program with Framework
1.1 was converted to 2.0, and on some computers almost every line of code is
up to 7 times slower than before! It has nothing todo with some special
topic like database access, it is really general!

I found out that deinstalling Framework 1.1 on some computers made the
application fast again, but unfortunately, that is not the case on every
computer.

We have this problem for several months and did not found the cause.

I think it must have something to do with an registry entry, which makes
every program step slow.

Thanks for any idea,
Bernd

"Bob Grommes" <bob@xxxxxxxxxxxxxx> schrieb im Newsbeitrag
news:O5qB5sFzGHA.476@xxxxxxxxxxxxxxxxxxxxxxx
Adeel,

If I understand you correctly, you developed the app on a computer that
you are working remotely via RDP or similar. This dev machine also houses
the SQL Server for the dev database. In this scenario it runs fine, but
when you deploy the app on a different machine where the SQL Server is no
longer local, it is unacceptably slow.

Also, if I understand you correctly, despite saying "it worked fine in
1.1", this is not an app originally authored under 1.1. It's a brand new
2.0 app. Maybe some of the techniques are the same as you used
successfully in 1.1, maybe even some of the actual code is the same, but I
think you may be wrong in attributing the success of that code to 1.1 and
its current failure to 2.0.

There can be dozens of reasons why you might be experiencing this issue.
From your very sparse explanation, I'd be tempted to suspect that your
database access code is not efficient, and this is masked sufficiently by
using a local DB server and/or small test data sets, that this didn't
become apparent until you deployed it in a different scenario.

However, such a conclusion would be premature. You really need to profile
the deployed application to determine where the bottleneck is. If it is,
in fact, I/O bound, then you would need to determine if that is some kind
of network issue, DB server configuration issue, issues with your own code
architecture, or some combination of those factors.

Until you gather facts and make a case, you're just taking shots in the
dark.

Don't get overly hung up on "it worked fine in 1.1", even if this is
strictly a 1.1 ==> 2.0 project conversion with no other changes. That is
not a helpful mindset in actually figuring out the issue. I think it's
safe to say that 2.0 is not likely to have major, insurmountable
performance issues relative to 1.1; I think it's safe to say that even the
2.0 app was fine on the dev machine. So ... focus not on the platform
version change, but on what is different between the dev and deployment
machines / networks / security, etc.

Sorry I don't have a magic wand for you ... unfortunately the way you are
approaching this problem solving exercise (jumping to conclusions, not
offering the kind of data / information one would normally offer in asking
for help for this kind of problem) suggests to me that you may need to
bring in someone with some problem solving experience in this particular
area to evaluate things.

--Bob

DiL wrote:
Hi Bob!
i have completly developed an application in 2.0 winforms,
it's working ok on the remote computer where i have developed it and
databse sql server 2000 is on same computer, it working well on that
pc, but when i run it on some other computer other than that computer
it's working really slow, even when i open a simple connection, it's
work really slow, while in 1.1 it was really working well, Bob have you
developed or converted such kind of distributed or developed, Also
Micheal is ur application like mine one and having such problem

well if any one has solution of that problem plz help me

Regards,
Adeel



.

Relevant Pages

  • Re: Performance issue after coverting from Framework 1.1 to 2.0
    ... In this scenario it runs fine, but when you deploy the app on a different machine where the SQL Server is no longer local, it is unacceptably slow. ... I think it's safe to say that 2.0 is not likely to have major, insurmountable performance issues relative to 1.1; I think it's safe to say that even the 2.0 app was fine on the dev machine. ... focus not on the platform version change, but on what is different between the dev and deployment machines / networks / security, etc. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: System_SR_ENU.cab
    ... > installing SQL Server CE 2.0, ... Then i decided to try and deploy the app onto ... cancel the installation your app will continue to run, ... If the Compact Framework was built into the device ROM then it won't appear ...
    (microsoft.public.windowsce.embedded)
  • Re: Newbie: Application development and .Net
    ... My company wanted to move from Access Databases to SQL Server. ... Can you use the .Net framework as a front end to SQL Server without ... your app has to access the framework. ...
    (microsoft.public.dotnet.faqs)
  • Re: C5 woes. How stable is VFP really?
    ... After that I close the SQL server cursor and work with my manual cursor instead. ... a VFP9 app on a really old machine ... app was under more "pressure", VFP showed ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Webservices - the way to go...?
    ... about your lack of secure network connectivity your between a rock and a ... To summarize the posts so far: you have a winform app. ... using a webservices data layer to handle all the database interactions. ... Upgrade your database to SQL Server. ...
    (microsoft.public.dotnet.general)
Loading