Replies: 3 comments 4 replies
-
|
Have you considered using one PathLayer per line, and then maintaining one buffer per line? Usually it's recommended to use one layer, as you've done, but anything under 256 should be fine (I think 256 is a soft cap and primarily matters when the app needs picking interactivity) |
Beta Was this translation helpful? Give feedback.
-
|
One question: how hard would it be to extend the data attributes mechanism to include |
Beta Was this translation helpful? Give feedback.
-
|
You might also consider Perspective for this use case. It focuses more on realtime traditional charting for large datasets. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have an application which periodically produces new batches of points for a number of existing lines. These lines can get quite long though (upwards of 1M points) although the total number of lines in a plot is modest (less than 10). A typical run may produce 100 new points every second or so.
At the moment, I was thinking to use PathLayer with:
but, then when new data arrives, unfortunately, since all of the data for any given line needs to be contiguous, I need to rewrite the entire buffer data.
For example, if my buffer contains data for lines A, B and C, and it initially looks like:
AAAABBBBCCCCCCC
then I receive new data AA, B, CCC, then I need to rewrite the whole thing as
AAAAAABBBBBCCCCCCCCCC
Is there any better way to do this in this situation?
Here is an example of data accumulated over about an hour, with two lines and 1M points per line (log log plot). This example is using Bokeh, but I wondered if deck.gl could be more flexible and performant.
Beta Was this translation helpful? Give feedback.
All reactions