Skip to main content
P
ptc-9539261-Visitor
1-Visitor
June 30, 2010
Question

Poor performance opening AE 5.4 M150

  • June 30, 2010
  • 14 replies
  • 1900 views
In our move to AE 5.4 M150, many authors are reporting very poor performance when first launching the editor. I've confirmed this even when opening the editor without a document. It takes anywhere from 40 to 90 seconds, usually the first time you open the editor. If you immediately close and then reopen the editor (again, without a document), it opens in just a few seconds. Anyone have any idea what's going on during that initial open. It has nothing to do with our doctypes, etc., as it happens without opening a document. Maybe there are some default preferences that need to be unplugged?

Again, this was not an issue with AE 5.2 M130, our previous level.

Dave

    14 replies

    Show previous replies
    P
    ptc-9539261-VisitorAuthor
    1-Visitor
    June 30, 2010
    The problem persists even if the CMS client is never opened. There are no java processes running prior to opening AE.

    No one reporting this problem is using VPN or accessing remotely. I'm having the problem with a dual-core laptop with 2 Mbytes of memory. Should be adequate, no?
    C
    ClayHelberg18-Opal
    18-Opal
    June 30, 2010
    Hi David-



    I don't know for sure, but I think it must be something to do with your
    configuration. I can start up 5.4 M050 in about 3 seconds on my main
    machine (Windows Vista), and in about 4 seconds on a Windows XP virtual
    machine. This is on a pretty basic laptop (that's about 2 years old), so
    I'm not "cheating" with a high-end workstation or anything like that.



    If you don't have any code in your custom/init directory, then the only
    thing I can think of is some kind of network issue, or maybe you're just
    running into a hardware issue. Are these machines skimpy on RAM or CPU
    power?



    What happens if you turn off your customizations (i.e. remove the
    APTCUSTOM environment variable)? Does it get faster then? If so, that's
    a further indication that it's something to do with your configuration
    rather than the application itself.



    --Clay


    P
    ptc-30501501-Visitor
    1-Visitor
    June 30, 2010
    We have the same with zero APT environment variables set on the local PC…and our setup sounds the same as David’s with file paths, only an instance.acl…and the random one-plus minute load times if editor has been off too long.

    John T. Jarrett CDT
    Senior Tech Writer, Integrated Logistics Support, Land & Armaments/Global Tactical Systems

    T 832.673.2147 | M 832.363.7234 | F 832.673.2376 | x1147 | -<">mailto:->
    BAE Systems, 5000 I-10 West, Sealy, Texas USA 77474
    www.baesystems.com
    A
    AndyEsslinger1-Visitor
    1-Visitor
    June 30, 2010
    Dave,



    Have you tried it on a PC or just the Laptop?



    Have you tried to run everything locally to eliminate the network latency?



    You should run from a PC if you are benchmarking things (or at least to
    eliminate the laptop as a possible problem). Laptops have their own set of
    problems. It takes my notebook 1-1/2 or 2 minutes to start Arbortext Editor
    (2.2 GHz duo CPU with 4 gigs of RAM and Windows XP Pro). Some of the factors
    are:



    How fast the laptop CPU is running (regardless of what it is labeled.)

    How fast the hard drive is (many or even most laptops have 5400 rpm or
    slower HDs. The one I have now is 7200, the previous laptop was 4800.

    What else is running (my laptop has 71 processes going when it finishes
    boot; my work PC has 54 and my home PC has 33 and they have 2.2 GHz CPUs
    with 2 gig of RAM).



    I opened a case a long time ago about 5.3m040 taking too long to start (I
    wish for fast times like 40 or 60 seconds). The resolution after a few days
    of troubleshooting was "we'll fix it some future release."



    I think you should open a ticket with PTC. I have a bookmark set to this
    site: <">https://www.ptc.com/appserver/cs/call_logger/call_logger.jsp>
    Terms & ConditionsAccessibility statement