clerk

Alex 2024-11-24T07:01:08.318029Z

Hi! I've passed a rather long seq (>7k elements) to clerk/vl 's :encoding ... :sort and got the error on the picture. Is it more likely a Clerk's issue or one of Vega itself? 🙂

Alex 2024-11-26T08:03:41.459899Z

@mkvlr I tried to (time) it and I see that indeed caching is in effect, as it should be. but it looks like Vega still renders from scratch and this is what I perceived as lack of caching. I'm rendering some ~40,000 data points — that's probably the reason why I'm noticing it. Is this by design, or could be optimized?

mkvlr 2024-11-24T18:45:59.299749Z

can you also paste the bottom part of the error?

Alex 2024-11-24T19:04:26.535439Z

cannot reproduce it exactly at the moment (getting `Maximum call stack size exceeded` in JS instead). IIRC, it was going like that all the way up to 7,000-something branches

Alex 2024-11-24T19:08:19.047989Z

btw, is it expected that clerk/vl charts are rendered from scratch with every file save, even if nothing relevant changed?

mkvlr 2024-11-24T20:50:59.367439Z

@alex.shulgin not expected, would you mind filing an issue? 🙏

Alex 2024-11-25T07:55:53.139469Z

@mkvlr sure. how do I go about actually measuring the time it takes to render a form? For now I only have a feeling that it takes much longer than I expect to see the "Evaluating cell 20 of 20: (clerk/vl {:data {:values ..." badge in the top-left corner.