Hi, Thanks for sharing problem. Yes, zeppelin-web is not really optimized at the moment.
For rendering table, following two functions from paragraph.js are related. loadTableData() - parse text output from backed by \n,\t and construct array for rows and columns. renderTable() - a lot of string concatenation. I didn't profiled them, but it may take some time for array construction and string concatenation. If you can help on it, that'll be really great. Thanks, moon On Wed, Jul 1, 2015 at 1:51 PM Andres Celis <[email protected]> wrote: > Hi Zeppelin team! > > I have been working on an interpreter for zeppelin that connects to MS SQL > Server. It is pretty much finished, but I had some questions as to the > scalability of Zeppelin and how to contribute. > > Recently I ran a select statement that pulls in ~45,000 rows from SQL > Server. Afterwards the application was extremely sluggish in its > performance (on chrome) and it would crash (on internet explorer). I was > hoping you could help me pinpoint where these problems occur so that I > could see if I could help make Zeppelin more scalable. > > Internet explorer would say there were "long running scripts" which were > making it sluggish, and when I was debugging I also saw that actions like > trying to "persist" or "save" the note were taking a while. I also wonder > whether the renderTable function in paragraph.js could be the culprit that > is slowing everything down since it uses a lot of string concatenation. > These are just starting points of what might be slow, I am still new to > zeppelin so I am hoping that with your experience you will have a better > understanding of what could be going wrong. > > Looking forward to working with you, > Andres >
