Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-4612

Optimize Notebooks loading

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 0.9.0
    • None
    • NotebookRepo
    • None

    Description

      Our current Notebooks base contains more than 1500 Notebooks.

      While in Zeppelin 0.8.3 the solution was not ideal because all Notebooks were loaded in memory at Zeppelin startup, the situation in Zeppelin 0.9 is worse because loading the Notebooks is occuring at login phase. So the end user has to wait a long long time before he is getting in Zeppelin and usually thinks that Zeppelin is down.

      Also, the solution of loading the entire Notebook base in memory is not scalable because as new Notebooks are created we always have to increase the ZEPPELIN_MEM environment variable.

      At the moment to be able to log in Zeppelin with our 1500 Notebooks we set: 

      ZEPPELIN_MEM=-Xmx8192m -XX:MaxPermSize=1024m
      

      This is a lot of memory that cannot be used for actual code processing.

      The first logging takes 42 sec (see logs from 2020-02-13 08:23:11 to 2020-02-13 08:23:53)

      Wouldn't be possible to just walk through the directory structure of the NotebookRepo to display Zeppelin welcome page with the tree structure?

      This would be a great improvement and would offer the possibility to use Zeppelin at scale.

       

      Attachments

        1. zeppelin--zeppelin.log
          1.87 MB
          Axel Van Damme
        2. log4j.properties
          1 kB
          Axel Van Damme
        3. zeppelin--zeppelin_2020-03-20.log
          2.46 MB
          Axel Van Damme

        Issue Links

          Activity

            People

              zjffdu Jeff Zhang
              dammeax Axel Van Damme
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m