4 ms·
Is that Ram only or also L1 etc. caches?
by chrisper 9y ago
Is that Ram only or also L1 etc. caches?
- frik 9y agoOkay, so how can we deactivate ASM.js and WebAssembly? (in the light of Meltdown and Spectre) The config in Chrome is broken, WebAssembly cannot be deactivated anymore with chrome://flags/#enable-webassembly , setting it to "deactivated" and it's still active.
- Marat_Dukhan 9y agoAsm.js is not necessary, simple JavaScript interpreter is enough. This demo used to work before most browsers implemented optimizers for Asm.js
- rmrfrmrf 9y agoYou need to disable `SharedArrayBuffer` and `performance.now`, which Firefox already did.
- based2 9y agoMozilla Foundation Security Advisory 2018-01 Speculative execution side-channel attack ("Spectre") https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-0...
- wyldfire 9y agochrome://flags/#enable-site-per-process is a mitigation that at least raises the bar a little. :/
- TickleSteve 9y agoIts characterising memory accesses, so it will show up the result of using all the caches in the system. You would typically see larger latencies when the caches are not being effective. Multiple humps will indicate the presence of multi-level caches.