T
Tibro
Guest
For a 10 years I am developing a program, ...still adding requested functions, still growing.
Code is more than 30.000 lines... but this is not the case.
The CASE is the DESIGNER file. On the Form with TabControl and lot of subTabs, there are more than 3.100! Controls...
and the Form.Designer.vb file has 51.000 lines!
But the problem is BEFORE the program starts - when it is "constructing" - adding the controls on the form (as I am just thinking)
Even when debbuging (F5 pressed) or even later running published .exe file, in both cases it still takes almost 40 seconds until the Form shows.
For those many years, It was tested on many HW configurations. This start delay of initial showing the Form to user takes really from 10 to 40 seconds.
Firstly I was calmed and thought the same as many of you might think now: "Yes, it is the question on CPU performance. Nothing more can by done. Ok
"
But-But-But! I think it is not the question of CPU power, because, it is strange, But is not the rule, but very often, on cheap low-end CPUs it runs better.
I have two comps only as an example:
On comp with i7-3740QM - 2.7Ghz (8334 benchmark points), 12GB RAM, SSD drive... takes >42< seconds the Form to show up.
On comp with Pentium E2220 - 2.4 Ghz (1486 !!!!!!! points), 2GB RAM, HDD drive... it takes ONLY >2< seconds for Form to show up.
What the heck!
And there are many more examples for those years. IT IS NOT the question of Computer performance. So What than is the question of???
To find out the reason of this great starting delay and search for some workaround, theese activities was taken:
The same fresh instalation of Visual Basic 2010 express on different computers with different HW and different OSes: W7-32bit, W7-64bit, W8, W10, Also the visual studio community 2017 was tested, visual studio preformance tips, cleaning the caches,...
...but at the end leaving all this labouring behind, because consider this again:
The published exe file executed alone (when VBstudio is closed, or even not installed) behave EXACTLY THE SAME (the same show up delay) as like the opened VB project when running/debugging.
So (I think) the Visual studio istself is out of the guilties.
Maybe some optimizing of designer.vb file can affect also the compiled exe, ...but the mindworm rises again:
"On that low-end crap it is done in 2 secs without optimizing...!!!"
Is someone out there, who knows, how can I achieve those 2 second delay also on those high end machines?
T.
Continue reading...
Code is more than 30.000 lines... but this is not the case.
The CASE is the DESIGNER file. On the Form with TabControl and lot of subTabs, there are more than 3.100! Controls...
and the Form.Designer.vb file has 51.000 lines!
But the problem is BEFORE the program starts - when it is "constructing" - adding the controls on the form (as I am just thinking)
Even when debbuging (F5 pressed) or even later running published .exe file, in both cases it still takes almost 40 seconds until the Form shows.
For those many years, It was tested on many HW configurations. This start delay of initial showing the Form to user takes really from 10 to 40 seconds.
Firstly I was calmed and thought the same as many of you might think now: "Yes, it is the question on CPU performance. Nothing more can by done. Ok
"But-But-But! I think it is not the question of CPU power, because, it is strange, But is not the rule, but very often, on cheap low-end CPUs it runs better.
I have two comps only as an example:
On comp with i7-3740QM - 2.7Ghz (8334 benchmark points), 12GB RAM, SSD drive... takes >42< seconds the Form to show up.
On comp with Pentium E2220 - 2.4 Ghz (1486 !!!!!!! points), 2GB RAM, HDD drive... it takes ONLY >2< seconds for Form to show up.
What the heck!
And there are many more examples for those years. IT IS NOT the question of Computer performance. So What than is the question of???To find out the reason of this great starting delay and search for some workaround, theese activities was taken:
The same fresh instalation of Visual Basic 2010 express on different computers with different HW and different OSes: W7-32bit, W7-64bit, W8, W10, Also the visual studio community 2017 was tested, visual studio preformance tips, cleaning the caches,...
...but at the end leaving all this labouring behind, because consider this again:
The published exe file executed alone (when VBstudio is closed, or even not installed) behave EXACTLY THE SAME (the same show up delay) as like the opened VB project when running/debugging.
So (I think) the Visual studio istself is out of the guilties.
Maybe some optimizing of designer.vb file can affect also the compiled exe, ...but the mindworm rises again:
"On that low-end crap it is done in 2 secs without optimizing...!!!"
Is someone out there, who knows, how can I achieve those 2 second delay also on those high end machines?
T.
Continue reading...