You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@zeppelin.apache.org by John Omernik <jo...@omernik.com> on 2016/04/06 23:20:59 UTC
Zeppelin Performance
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
Re: Zeppelin Performance
Posted by John Omernik <jo...@omernik.com>.
There were not a large number of notes, I think there may have been some
other things going on, my performance has been better except one thing.
Often times when I go to click on a note to enter text or update text, it
can take a number of mouse clicks before the cursor focus actually happens
for me... this MAY still be laggy response, or it may be something with my
browsers/computers (I am using Firefox and Chrome on a well equipped Mac
OS). Do others experience this as well? Just trying to determine what may
be at fault here....
On Sat, Apr 16, 2016 at 2:28 AM, vincent gromakowski <
vincent.gromakowski@gmail.com> wrote:
> +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 <mo...@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 <jo...@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
>>>
>>>
>>>
>
Re: Zeppelin Performance
Posted by vincent gromakowski <vi...@gmail.com>.
+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 <mo...@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 <jo...@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
>>
>>
>>
Re: Zeppelin Performance
Posted by moon soo Lee <mo...@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 <jo...@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
>
>
>