Nope, neither do I and at the time I can't imagine how can anything else but browser implementation be tested (well, we could probably compare features after we identify exactly what we want). The only solution that I see for this is that we try to find a few common cases that we can test (10k nodes, 10k nodes randomly moving, 10k nodes moving and changing colors, 10k nodes interconnected, 10k nodes interconnected and moving, etc.) and try to implement them (or at least a couple of subsets of it), hopefully without wasting too much time on them. With a bit of luck we will get some reasonable numbers without too large deviations.But I don't know any benchmark for comparing WebGL libraries in term of FPS or features - only tests for browsers implementations. I think this largely depends on others factors like the layout algorithm and graph/ressource loading performance (data format and compression, server charge, bandwidth..)
Statistics:Posted by Neo--- — 05 Apr 2011 21:54
Statistics:Posted by jbilcke — 04 Apr 2011 12:58
Statistics:Posted by keheliya — 04 Apr 2011 02:25
Statistics:Posted by jbilcke — 03 Apr 2011 22:20
Statistics:Posted by mbastian — 28 Mar 2011 23:19
Statistics:Posted by Neo--- — 28 Mar 2011 18:40
You can find a blog post here I wrote about getting WebGL to work in Chrome 10+ and Firefox 4. Hope it'll be beneficial to many, who are having the same problem.joshua wrote:That didn't work, but some more Googling discovered that it had been added to a blacklist and you could get around that blacklist with
Statistics:Posted by keheliya — 24 Mar 2011 03:46
We have considered this (see this topic), these librairies offer great features and flexibility but they are not performant enough for large graphs. The limits would be around 5000 nodes, and the experience limited, as zooming and panning speed would be reduced.I would like to know whether this project's scope cover considering other alternatives like d3.js and processing.js too for visualizing large networks on the web
Statistics:Posted by mbastian — 21 Mar 2011 04:54
CODE:
google-chrome --enable-webgl
CODE:
google-chrome --enable-webgl --ignore-gpu-blacklist
Statistics:Posted by joshua — 19 Mar 2011 23:28
Statistics:Posted by keheliya — 19 Mar 2011 02:30
Statistics:Posted by mbastian — 05 Apr 2010 18:08
Statistics:Posted by juliana — 05 Apr 2010 05:02
Statistics:Posted by fat0ss — 30 Mar 2010 15:21