Closed Bug 975132 Opened 12 years ago Closed 11 months ago

IonMonkey: investigate THREE.js optimization (slow Vector3 properties)

Categories

(Core :: JavaScript Engine: JIT, defect, P3)

Product:
Core
Component:
JavaScript Engine: JIT
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1953915

People

(Reporter: djvj, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

I'm not sure if this is a problem with THREE.js, or an optimization issue. I ran into this while trying to help with some demos for MWC. In particular the JIT Inspector revealed that a lot of hot-path assignments to the properties |x|, |y|, |z|, and |w| of Vector3 were converted to GetElementCache operations instead of StoreFixedSlot operations. This should be investigated and fixed, whether it's bad code in the library, or bad optimization choices being made by Ion.
THREE.js is used a lot, especially in WebVR code, so ensuring that we're not slow at it for possibly stupid reasons would be nice.
Blocks: sm-js-perf
Priority: -- → P3
Keywords: perf
Severity: normal → S3

bug 1953915 is more recent. I will just dupe this over.

Status: NEW → RESOLVED
Closed: 11 months ago
Duplicate of bug: 1953915
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.