- I’m on R8.5.1FP3 and can’t migrate at present, but this thing redefines slow. If I’m loading a tiny do-nothing application from a server on the LAN it’s lightning fast. Less than a second. Tiny do-nothing application.- But I’m loading a complex enterprise level application from a remote server, and DDE just took a full NINTY-NINE seconds to load up. Sure it painted the screen in a “mere” 27 seconds, but my experience is if I try to do anything before the “crawling blocks” are done one of three things happens:
-
It’s slower than molasses in January, such that best case I might get one element opened and scrolled to position before the “crawling blocks” go away, at which time it speeds up.
-
It does nothing what-so-ever until the “crawling blocks” go away, anyway, so I should have just waited.
-
DDE tosses an Exception. This happens about 15% of the time.
-
In essence it’s simply not worth it to attempt to do anything with DDE until the “crawling blocks” go away, and that takes an inordinate amount of time.
-
Even if I open this template from local it takes over 40 seconds for the “crawling blocks” to get done. Local! I have two cores and 4GB RAM with 786MBytes assigned to DDE. I could copy this 12MB template numerous times in 40 seconds, yet DDE barely opens it in that amount of time.
-
This EXACT same database opens in R6.5.4, remotely, in Designer, in UNDER FOUR SECONDS.
-
Under four seconds vs ninty-nine seconds. A minimum of 25 times slower for the exact same operation.
-
I know about the Java Tooling and all the gobbedly-gook it does on load. I don’t care. I just want to work instead of sitting on my thumbs staring at the little crawling blocks for what seems like immense quantities of time. Even if R8.5.2 cuts this load time in half, it’s still more than a full order of magnitude slower than R-prior. That is simply not acceptable for maintaining a complex enterprise grade application.
-
Thanks for your time…