Announcement

Collapse
No announcement yet.
X
Collapse
  • Page of 1
  • Filter
  • Time
Clear All
new posts
Previous template Next
    #1

    SmartGWT startup times - FAO Blama

    Hi Blama ,

    Hope you don't mind me singling you out for a question as you appear to be an active user who I assume has production level software using SmartGWT for the UI. (Can't see a way to post you a private message) but anyone's input would also be welcome.

    We have been having a real issue we startup times in dev mode and the business now is becoming interested and concern about the time wasted waiting for our application to start.
    Average Startup Time 25 Minutes (With slower processors, there is a few developers whose dev environment takes over an hour)
    GWT Version 2.7.0
    SmartGWT Version 5.1p (Power Edition) (Build Date : 01/12/2016 06:19)
    Java Version 1.8
    Client class files Around 1200
    IDE Intellij IDEA
    Build Tool Maven
    GWT Modules The application is just one Module

    So I'm just curious to know, how long does it take you application to startup in GWT dev mode, do you use Super Dev mode or the legacy dev mode (we all use legacy dev mode here as super dev mode takes couple the time to start up) Would be really good if you could share your experience and your setup when running dev mode.

    We saw a big jump in startup time when I converted the maven project to a multi module maven project, I still need to investigate if it was doing that that effect the time, or something in the same release that bumped the time up, but if you do use maven for your builds, would be interesting to know how your maven build is structured.

    Thanks,
    Dale

    Tags: None
    #2
    Hi ellisd5,

    to me, this looks like there is another problem - 25min can't possibly be OK.

    My project is based on BuiltInDS (started from there and extended it) and I run normal 2.7.0 Classic Dev Mode in FF26.
    Super Dev Mode is no option for me because of this issue. The issue might be Windows related, or Eclipse related only, but I did not bother testing further.
    In general SDM would be super fast for changes (but a bit slower startup than Classic Dev Mode) if it were not for the unnecessary static file copy operations.

    I'm using a fast CPU with Single-Thread-speed focus (Core i7-6700) and 12GB RAM under Win 10/Java 8/Eclipse Oxygen and the Dev Mode startup is about 20sec for the Plugin, the call itself in FF26 is again about 20 sec.
    After a change of the SmartGWT nightly it is way more, about 3min for the 1st call in FF26. I do have about 300 client side java files.

    I do compiles using Ant and a compile with war and deploy takes about 2min. The war file is approx 50MB. I have 15 permutations to compile (5x DE/EN/Default).
    Again, after the change of the SmartGWT nightly it is way more, about 5min.

    Assumptions:
    • PC to slow (I started on a old Laptop and there the times were 2-2.5x higher)
    • Some gwt-unitCache issue (perhaps this gets cleaned every time?)
    • Way more permutations to compile (don't know if this can be an issue in Dev Mode)
    • Environment (OS (?) / Intellij IDEA) related issue (how long does the Classic Dev Mode start for BuiltInDS take you? 1st startup, 1st call in FF26, subsequent startup, subsequent call in FF26)
    Best regards
    Blama

    Comment

      #3
      Thanks very much for your reply,

      I'll try running that bultin-ds sample and when I get a minute, I just tried to run it quickly but project didn't import cleanly, it did seem to do the compile however and that took, 10-15 seconds. I''ll have a look at gwt-unitCache, must admit I don't what that is, but I'll have a read. Compilation wise, pretty sure it only does 5.

      Don't know if you ever turn on the trace logging for compile, shame I can't get more information out of it to tell me what its doing so I can see where the time goes!

      logging (-logLevel TRACE)
      TRACE: Compiling...
      TRACE: 0% complete (ETR: ?)
      TRACE: 10% complete (ETR: 2420 seconds)
      TRACE: 20% complete (ETR: 1399 seconds)
      TRACE: 30% complete (ETR: 940 seconds)
      TRACE: 40% complete (ETR: 774 seconds)
      TRACE: 50% complete (ETR: 564 seconds)
      TRACE: 60% complete (ETR: 454 seconds)
      TRACE: 70% complete (ETR: 315 seconds)
      TRACE: 80% complete (ETR: 199 seconds)
      TRACE: 90% complete (ETR: 118 seconds)
      TRACE: 100% complete (ETR: 0 seconds)
      TRACE: Compilation completed in 1136.94 seconds (18 Minutes)
      Last edited by ellisd5; 5 Oct 2017, 06:03.

      Comment

        #4
        Hi Blama ,

        Your previous post pointed me in the direction of the gwt-unitCache, which turns out there is a bug in the IDEA where the cache is cleared on startup. My startup time is now 4 minutes, much better

        Comment

          #5
          Hi ellisd5,

          OK, that sounds like a huge improvement. How does the 4 minutes compare to a non-1st start of BuiltInDS?
          IMHO the class count is not that important for startup, but I might be wrong.

          If it is also around 3-4min, you might get further improvements by having a look at the other suggestions (especially high-GHz CPU).


          Best regards
          Blama

          Comment

            #6
            Or, if #4 is BuiltInDS and not your app, then you should definitely have a look at the other suggestions.

            Comment

            Previous template Next
            Working...
            X