Evaluate SharedArrayBuffer for shared memory with web workers
Open
category - 3d tiles
category - architecture / api
category - terrain and imagery
type - enhancement
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
Still being standardized, but there are experimental implementations in at least Chrome and Firefox.
https://hacks.mozilla.org/2016/05/a-taste-of-javascripts-new-parallel-primitives/
Enable in Firefox:
> about:config
javascript.options.shared_memory
Enable in Chrome:
> chrome://flags/
shared-array-buffer
The above demo does not run in Chrome; I did not investigate.
Contributor guide
Research direction
Start by reading the linked Mozilla article and reproducing the referenced demo with SharedArrayBuffer enabled in Firefox and Chrome using the listed configuration pages. Compare the demo’s behavior in both browsers and document whether shared memory with web workers is viable for Cesium, including the Chrome failure noted in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100