[IPython-dev] [sage-devel] Re: Jupyter notebook by default?

MinRK benjaminrk at gmail.com
Wed Jan 6 07:16:51 EST 2016


On Wed, Jan 6, 2016 at 1:02 PM, Volker Braun <vbraun.name at gmail.com> wrote:

> On Wednesday, January 6, 2016 at 11:55:36 AM UTC+1, Min RK wrote:
>>
>> If we truncate instead of virtual-scroll, then we have a choice for
>> whether truncated output is included in the document or not, which
>> alleviates the problem of opening notebooks that have a problematic amount
>> of output
>>
>
> There is no fundamental problem with large amounts of output (really, any
> content), and there is essentially only a single way to do it right:
>
> The view (dom) needs only a fixed number of dom nodes for a virtual scroll.
>
> The in-browser view model can lazily load the current scroll position,
> with a suitable cache. Fixed amount of browser JS memory.
>
> The server can just mmap the output file, or alternatively seek around in
> the file. With a suitable index. Fixed amount of server-side memory.
>

Files aren't used for output. The filesystem should only be involved, if at
all, in the exceptional case of output overflow.


>
> The kernel has to block if the notebook server can't append output fast
> enough, thats normal flow control just like in a pipe. Fixed memory usage
> in the kernel.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/8erxWppKxXM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscribe at googlegroups.com.
> To post to this group, send email to sage-devel at googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20160106/f514ae7d/attachment.html>


More information about the IPython-dev mailing list