Thanks for the confirmation. It’s a fascinating technical milestone, but if we are looking to resources conservation, this is clearly not the right direction...
On Saturday, February 14, 2026 at 1:36:39 PM UTC+1 [email protected] wrote: > SageMath-in-Browser is about 2 orders of magnitude slower than native sage > code. > I ran the following bench mark: > 'from sage.misc.benchmark import *' > '_ = benchmark()' > > Output of SageMath-in-Browser: > [image: benchmark.png] > Output of native sage: > [image: bench_native.png] > On Saturday, February 14, 2026 at 4:55:39 PM UTC+8 Georgi Guninski wrote: > >> > I don't know the expected performance penalty. >> >> To measure the time, create `file.sage` with fast code. >> In bash run: time sage file.sage # for native sage >> and: time emulated_sage file.sage #for JS sage >> >> To benchmark inside sage, one possibility is: >> sage: timeit("code") >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/91b2b37a-9dd8-4249-8fdc-509e89c0492cn%40googlegroups.com.
