Heh. Yes, it is only an "aim" I suppose.

Yes. My code is single threaded. I note that threading will be added to the 
WASM spec in the near future so maybe there will be opportunity for me 
there when the change is added to the Go compiler.

I'll put this issue to rest for now and revisit it in a few months.

Thanks

On Saturday, 23 September 2023 at 09:53:34 UTC+1 TheDiveO wrote:

> The cynic in me notes the use of "aims".
>
> IIRC is single-threaded, do you know if your code is single- threaded too, 
> or does it use several core for decoding? 
>
> On Saturday, September 23, 2023 at 7:37:13 AM UTC+2 Stephen Illingworth 
> wrote:
>
>> Comparison to native speeds is the key attraction of WASM. From the 
>> go.org blog published 10 days ago: https://go.dev/blog/wasi
>>
>> "WebAssembly (Wasm) <https://webassembly.org/> is a binary instruction 
>> format originally designed for the web. It represents a standard that 
>> allows developers to run high-performance, low-level code directly in web 
>> browsers at near-native speeds."
>>
>> And from the front page of webassembly.org
>>
>> "The Wasm stack machine <https://webassembly.org/docs/semantics/> is 
>> designed to be encoded in a size- and load-time-efficient binary format 
>> <https://webassembly.org/docs/binary-encoding/>. WebAssembly aims to 
>> execute at native speed by taking advantage of common hardware 
>> capabilities 
>> <https://webassembly.org/docs/portability/#assumptions-for-efficient-execution>
>>  
>> available on a wide range of platforms."
>>
>>
>> On Saturday, 23 September 2023 at 01:18:26 UTC+1 Robert Engels wrote:
>>
>>> Typically WASM performance is compared to JavaScript - ie. faster than 
>>> JavaScript usually 1.5-10x. 
>>>
>>> People don’t usually compare WASM with native apps. 
>>>
>>> On Sep 22, 2023, at 7:04 PM, Robert Engels <ren...@ix.netcom.com> wrote:
>>>
>>> 
>>>
>>> WASM goes through the browser - so it is very different. Are you using 
>>> OpenGL or similar?
>>>
>>> On Sep 22, 2023, at 3:44 PM, Stephen Illingworth <stephen.i...@gmail.com> 
>>> wrote:
>>>
>>> 
>>> I'm comparing the results of a program compiled for AMD64 and WASM 
>>> architectures. The code is the same except for the change of architecture. 
>>> The size of the difference in performance is unexpected to me but maybe 
>>> it's normal.
>>>
>>> On Friday, 22 September 2023 at 20:16:20 UTC+1 Robert Engels wrote:
>>>
>>>> When you say negative performance are you talking about a native app 
>>>> running directly on the hardware what are you referring to exactly
>>>>
>>>> On Sep 22, 2023, at 1:03 PM, Stephen Illingworth <
>>>> stephen.i...@gmail.com> wrote:
>>>>
>>>> 
>>>>
>>>> I've been thinking some more about this problem this week. I found the 
>>>> performance profiler in Chrome and can see that the each frame is taking 
>>>> longer than the required 16.7ms to create. The duration for each frame is 
>>>> more like 100ms. The native performance meanwhile can reach about 7ms. I 
>>>> expected a drop in performance but not that much.
>>>>
>>>> If anyone can offer any insight or if these figures seem wrong then I'd 
>>>> love to take some advice.
>>>>
>>>> Regards
>>>> Stephen
>>>>
>>>> On Saturday, 16 September 2023 at 09:02:34 UTC+1 Stephen Illingworth 
>>>> wrote:
>>>>
>>>>> I have tried running it in Firefox and Chromium. The webserve.sh 
>>>>> script in the ebiten_test folder runs a small httpd server to serve up 
>>>>> the 
>>>>> binary to the browser.
>>>>>
>>>>>
>>>>>
>>>>> On Saturday, 16 September 2023 at 08:45:52 UTC+1 Brian Candler wrote:
>>>>>
>>>>>> What WASM runtime are you using to execute the code?
>>>>>
>>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "golang-nuts" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to golang-nuts...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/golang-nuts/d8926ffb-9ca3-48ac-aabc-76a8a43947dan%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/golang-nuts/d8926ffb-9ca3-48ac-aabc-76a8a43947dan%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "golang-nuts" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to golang-nuts...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/golang-nuts/1123a2da-3862-4da8-baf5-bc67dd2b7e6en%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/golang-nuts/1123a2da-3862-4da8-baf5-bc67dd2b7e6en%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/c26cc5d6-447c-4a04-8411-056f1f3d1809n%40googlegroups.com.

Reply via email to