Thanks Ahyoung & Corneau for both of your quick replies! My document has about 1000 words, 10 code blocks, and it takes 6 seconds to render in Safari. It actually crashes in Chrome... My computer is a 2015 MBP which should be capable.
To be more specific, I just found that the code blocks took most of the render time. If I remove the 4 longest ones (each with 5-10 lines of code), it will be lightening fast. Zhong On Tue, Feb 2, 2016 at 6:43 PM, Corneau Damien <cornead...@gmail.com> wrote: > @Ahyoung He meant that he is writting markdown using zeppelin interpreter > :) > > I actually never tried with a lot of lines, of long does it take? If its > really long, that might be worth opening an issue > On Feb 2, 2016 6:27 PM, "류아영" <fbdkdu...@nflabs.com> wrote: > >> Hi Zhong, >> Thank you for the markdown interpreter documentation! >> >> I don't know the exact reason why your browser get stuck without >> response. 😢 >> Zeppelin use jekyll >> <https://help.github.com/articles/using-jekyll-with-pages/#installing-jekyll> >> when it builds documentation website. Did you see and try this README.md >> <https://github.com/apache/incubator-zeppelin/blob/master/docs/README.md> >> in Zeppelin github ? >> You can follow some instructions in this file, and then browse >> http://localhost:4000. Using this, you may see and test your >> documentation. >> Hopefully it could help you. >> >> Best regards, >> Ahyoung >> >> On Wed, Feb 3, 2016 at 11:05 AM, Zhong Wang <wangzhong....@gmail.com> >> wrote: >> >>> Hi guys, >>> >>> I am writing some documentation in Zeppelin using the md interpreter, >>> and found that it is pretty slow to render. The documentation is not very >>> long: less than 1000 words with some code. I tried both Safari and Chrome, >>> and it seems Chrome is slower: browser get stuck without response for quite >>> a while. >>> >>> Is there any way to display documents faster on Zeppelin? >>> >>> Thanks! >>> >>> Zhong >>> >> >>
