+1 for the optimization of the UI with the update after action. we have some remote users over a laggy entreprise network...
2016-04-16 7:14 GMT+02:00 moon soo Lee <m...@apache.org>: > Hi John, > > Thanks for sharing your feedback. > Could you share how big your 4 notes are? > > Laggy response might comes from two different reasons. > > First one is size of notebook. Zeppelin front-end built-on AngularJS 1.x. > And performance of front-end depends on number of watcher. While more > paragraph creates more watcher, large size of notebook may cause laggy > response. In this case, we can try optimize the front-end [1] > > > Second one is network delay between your browser and ZeppelinServer > daemon. Most of action you made inside notebook (run, hide/show output, > change graph, etc) is send to ZeppelinServer, and ZeppelinServer broadcast > response back to all connected browsers. Your browser is not updated when > you make an action, but updated when browser got broadcast response from > ZeppelinServer. > For this reason, with large network delay between the browser and > ZeppelinServer, user will experience some laggy action. > This case, we can improve front-end, immediately update ui after action, > before getting broadcast response. > > Hope this helps. > > Thanks, > moon > > [1] > https://www.google.com/search?q=angularjs+performance+optimization&oq=angularjs+performance+optimization&aqs=chrome..69i57.378j0j1&sourceid=chrome&ie=UTF-8 > > > On Wed, Apr 6, 2016 at 10:21 PM John Omernik <j...@omernik.com> wrote: > >> As I am getting back into the swing of things with Zeppelin, I am liking >> it more and more! Great work community! >> >> One thing I have noticed is with as few as 4 notes, I can start getting >> some laggy response from my browser (Firefox). Since I am new, I am going >> to assume it's something in my configuration, but in general, if my browser >> is laggy, are there any good documents on which settings to tweak, how to >> address these issues etc? If there are any good tips, or documents, I >> would be very appreciative. >> >> John >> >> >>
