Window is slow to instantiate - only on some machines
-
I have an app the has a large complex window (it edits documents) that uses Pegasus controls. On several of my machines the window opens in about 3 seconds. With one particular customer it takes almost 11 seconds. They have just about the same hardware and O/S as I do (XP, sp 3). I had them install more memory, and that didn't help either. I have added code to time events down to the millisecond - and have found the problem lies in the creation of the window. Loading the data and images is no problem - the times on all machines is about the same. Any ideas?
-
I have an app the has a large complex window (it edits documents) that uses Pegasus controls. On several of my machines the window opens in about 3 seconds. With one particular customer it takes almost 11 seconds. They have just about the same hardware and O/S as I do (XP, sp 3). I had them install more memory, and that didn't help either. I have added code to time events down to the millisecond - and have found the problem lies in the creation of the window. Loading the data and images is no problem - the times on all machines is about the same. Any ideas?
I tell such people to buy better computers. If it takes that long, it takes that long. Does it take that long every time, or just the first time ?
Christian Graus Driven to the arms of OSX by Vista. "I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )
-
I have an app the has a large complex window (it edits documents) that uses Pegasus controls. On several of my machines the window opens in about 3 seconds. With one particular customer it takes almost 11 seconds. They have just about the same hardware and O/S as I do (XP, sp 3). I had them install more memory, and that didn't help either. I have added code to time events down to the millisecond - and have found the problem lies in the creation of the window. Loading the data and images is no problem - the times on all machines is about the same. Any ideas?
Hi, look at Task Manager Performance for the CPU load while the app is starting. If it is around 100% all the time, your app is wasting CPU cycles for some reason (do you have busy loops? polling loops?); if it is around 50% all the time, your app is busy and might be faster with more multi-threading (assuming you have a multi-core CPU); if it is rather close to zero for some time, you are waiting for something (are you accessing stuff on servers? on Internet?).
dBrong wrote:
the problem lies in the creation of the window.
Then add more observation points until you got to the specific line that causes the delay. :)
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
-
I tell such people to buy better computers. If it takes that long, it takes that long. Does it take that long every time, or just the first time ?
Christian Graus Driven to the arms of OSX by Vista. "I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )
-
Hi, look at Task Manager Performance for the CPU load while the app is starting. If it is around 100% all the time, your app is wasting CPU cycles for some reason (do you have busy loops? polling loops?); if it is around 50% all the time, your app is busy and might be faster with more multi-threading (assuming you have a multi-core CPU); if it is rather close to zero for some time, you are waiting for something (are you accessing stuff on servers? on Internet?).
dBrong wrote:
the problem lies in the creation of the window.
Then add more observation points until you got to the specific line that causes the delay. :)
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
-
Is there a way to preload the Pegasus Dll's? Some users have delays of 11-20 seconds in the mybase.new method.
I'm not familiar with Pegasus, so I can't tell; you might contact the vendor about it. Is there some license scheme, possibly contacting them in real-time over the Internet? :)
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
-
So, it's Pegasus you need to talk to, right ?
Christian Graus Driven to the arms of OSX by Vista. "I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )