Title: vertices and indices out param support · Issue #4 · InteractiveComputerGraphics/splashsurf · GitHub
Open Graph Title: vertices and indices out param support · Issue #4 · InteractiveComputerGraphics/splashsurf
X Title: vertices and indices out param support · Issue #4 · InteractiveComputerGraphics/splashsurf
Description: So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms. As apart of perf investigations, I'm wondering if we can reduce some of this overhead by providing a ...
Open Graph Description: So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms. As apart of perf investigations, I'm wondering if we can redu...
X Description: So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms. As apart of perf investigations, I'm wondering if we ...
Opengraph URL: https://github.com/InteractiveComputerGraphics/splashsurf/issues/4
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"vertices and indices out param support","articleBody":"So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms.\r\n\r\nAs apart of perf investigations, I'm wondering if we can reduce some of this overhead by providing a vertices and indices out param, perhaps something like:\r\n\r\n```rust\r\nsplashsurf_lib::reconstruct_surface_with(&positions, ¶ms, &mut vertices, &mut indices)\r\n```\r\n\r\nThis should reduce some pressure on the allocator?","author":{"url":"https://github.com/whiterabbit42k","@type":"Person","name":"whiterabbit42k"},"datePublished":"2020-12-09T22:10:39Z","url":"https://github.com/InteractiveComputerGraphics/splashsurf/issues/4"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:34bc7506-7f51-e8b3-f1b3-cdf729838f86 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EB88:17415E:EC1C5:1470BB:6B00632B |
| html-safe-nonce | df7565dc8718bcf742a8e0b86bf007bb1bf413168762cb7cb5b889b07148beea |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQjg4OjE3NDE1RTpFQzFDNToxNDcwQkI6NkIwMDYzMkIiLCJ2aXNpdG9yX2lkIjoiNDYwMDMzNDY1Nzg4MjQ0ODY4MyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 6d4bacfe5325c0d9c087203758d9777cdf1bd5b04942e71e47a283970b7ae085 |
| hovercard-subject-tag | issue:760710246 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/InteractiveComputerGraphics/splashsurf/4/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c38c892c197908390a9673aac57ffaf1fd3ecb4c9729ee8fc26444972aa4c47a/InteractiveComputerGraphics/splashsurf/issues/4 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c38c892c197908390a9673aac57ffaf1fd3ecb4c9729ee8fc26444972aa4c47a/InteractiveComputerGraphics/splashsurf/issues/4 |
| og:image:alt | So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms. As apart of perf investigations, I'm wondering if we can redu... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | whiterabbit42k |
| hostname | github.com |
| expected-hostname | github.com |
| None | 25854482a1773a7c1ebb8be3d2bc1c6e61d82d78126be63b5044474a86d44d9e |
| turbo-cache-control | no-preview |
| go-import | github.com/InteractiveComputerGraphics/splashsurf git https://github.com/InteractiveComputerGraphics/splashsurf.git |
| octolytics-dimension-user_id | 18286040 |
| octolytics-dimension-user_login | InteractiveComputerGraphics |
| octolytics-dimension-repository_id | 246888911 |
| octolytics-dimension-repository_nwo | InteractiveComputerGraphics/splashsurf |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 246888911 |
| octolytics-dimension-repository_network_root_nwo | InteractiveComputerGraphics/splashsurf |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | e4f5c239e31f1f680e6bbc419ff92d774da616ec |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width