-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving performance for extremely large datasets #202
Comments
used the 3rd advice from #181 of setting warmupTicks={100} and cooldownTicks={0}, also turned off bloom postprocessing. it's working now, but the fps is still choppy + it took around 5 minutes before i could see the structures (it was a white screen before that). |
Those screenshots look stunning! You're probably pushing your hardware to its limits by rendering so many objects. 😄
|
hey, i used your suggestions and there was a moderate performance boost. i'll be using a few of my friends' powerful computers to render the model and hopefully take a few videos of it. i'm closing this issue now, i'll be commenting a link of our video (i'll credit you) as soon as it's done. thanks for the help! |
This looks pretty cool. Would you be able to share the source for the bloom post processing by any chance? I'm having trouble getting it to work. |
@TheAussieStew there is an example of it here. Relevant code: react-force-graph/example/bloom-effect/index.html Lines 28 to 34 in 153ab1f
|
Ah thank you! I looked at that example but I'm having trouble getting useRef to work with Typescript. Looks like I'll just have to experiment. |
a meaningful update.me and my friends used this library and made this video some time back. this 3d graph only had around 10k to 20k nodes. some of the issues, as i mentioned here, were FPS drops. to fix this issue, we used an open source AI project that transforms low FPS footage to high FPS (DAIN) -- however this proved to be problematic since there were lots of artifacts. eventually, we settled on producing this video with the shoddy footage and calling it a day. it was only a month later that we thought about timelapse-ing the whole project. so, essentially, i wrote a small script with rotated + panned + zoomed on the graph extremely slowly, slapped on OBS recorder on top of it, recorded for an hour and sped up the footage by 10x to 100x. the result was nothing short of fascinating. we still haven't released this footage yet, because we got distracted and might work on it in the future, but to anyone else wanting to make a video on extremely large 3d graphs using this library -- this is the best way you can do it, and the results will be insanely beautiful. i'll add a short video clip soon, once i get hold of my old hard drive. :) |
hey, i'm attempting to display a large dataset (117,927 nodes and 117,921 links), but WebGL runs out of memory after the first few seconds. is there any way to optimize the model or the animation to reduce/eliminate crashes, fps throttling, memory hogging?
The text was updated successfully, but these errors were encountered: