JavaScript InfoVis Toolkit 能够处理大量数据
有人有使用 JavaScript InfoVis Toolkit 显示大量数据的经验吗？基本上，我正在研究我的项目如何提供社交网络的视觉表示...并使用 JavaScript InfoVis Toolkit 我没有注意到任何性能下降...同时我看到了这个：
JavaScript InfoVis Toolkit - 交互似乎有点慢，也许这是演示中故意的 用于关系可视化的 javascript 框架
和
JsVIS 非常好，但对于较大的图形来说有点慢。从 JavaScript 中的图形可视化库
这让我担心在真实数据下它可能会破解？所以只是问一下..
加上我看了Flare，这似乎是另一个不错的选择，但看看他们的网站，它看起来好像已经近两年没有更新了......它完全过时了吗？
Does anyone have experience displaying large set of data using JavaScript InfoVis Toolkit? Basically, I am doing research on how my project can provide visual representation of social network... and playing around with JavaScript InfoVis Toolkit I did not notice any performance degradation... meanwhile I saw this:
JavaScript InfoVis Toolkit - interaction seems a little slow, maybe that's on purpose in the demos from
javascript framework for relationship visualization
and
JsVIS is pretty nice, but a little slow with larger graphs. from
Graph visualization library in JavaScript
this makes me worry that under real data it might crack? So just asking..
plus i looked at Flare, it seems like another good alternative, but looking at their site it looks like it hasn't been updated in almost 2 years... is it totally outdated?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
回答我自己的问题...性能并不是那么好。我写了一个脚本来填充 100 个节点的 ForceDirected 对象中使用的 json 对象，但速度非常慢...将尝试 www.graphviz.org。
To answer my own question.... performance is not that great. I wrote a script to populate json object used in ForceDirected object with 100 nodes and it was terribly slow... will give www.graphviz.org a try.
如果不使用渐变背景和其他消耗处理器的可视化之类的东西，它就足够快了。
我制作了 3 个级别和大约 100 个节点的 Sunburst。够快。
It's quick enough if not using such things like gradient background and other processor consuming visualisation.
I made Sunburst with 3 levels and about 100 nodes. Quick enough.
好吧，我在这里完全有偏见（免责声明：我是它的作者），但是 KeyLines 可以处理多个一百个节点就好了——它是商业许可的。
一般来说 - 除了选择什么框架的问题 - 我发现画布性能很大程度上取决于浏览器+设备是否具有硬件加速。例如，在 iOS5 之前，iPad 在 Safari 中画布的性能确实很糟糕，但自从 iOS5 以来，它的表现就突飞猛进。 Android 的变化更大。现在，大多数浏览器/操作系统的桌面组合都适合高性能画布渲染。
图形布局的另一个考虑因素是长时间运行的布局是否会阻塞浏览器的渲染循环 - 我们必须围绕长时间运行（即超过几秒）任务锁定浏览器的问题进行开发。用户喜欢看到进度条滴答作响&只要您在布局代码中采取正确的步骤，这是可能的。
OK, I'm totally biased here (disclaimer: I'm an author of it), but KeyLines can handle several hundred nodes just fine - it is commercially licensed.
In general terms - aside from the issue of what framework to choose - I've found that canvas performance depends strongly on whether the browser+device has hardware acceleration. For example, before iOS5, iPad performance for canvas in Safari really was dreadful, but since iOS5 it flies along. Android is more variable. Most desktop combinations of browser/OS are now fine for high performing canvas rendering.
Another consideration for graph layouts is whether long running layouts block the browser's rendering loop - we've had to develop around the issue of long running (i.e., more than a few seconds) tasks locking up the browser. Users like to see progress bars ticking along & that is possible provided you take the right steps in the layout code..