Active Topics

 


Reply
Thread Tools
Posts: 542 | Thanked: 117 times | Joined on Sep 2008 @ 52 N, 6 E
#1
This javascript big number page

http://tools.velp.info/bignumber.html

can calculate large numbers with precision only limited by processor speed.

I calculated 2^1000 (301 digits) on four N810 browsers:

MicroB: 22.5 sec
Fennec: 11.3 sec
Midori and Tear: 5.7 sec.

The latter two have a webkit engine.
__________________
Nokia N810 FW version 5.2008.43-7
iPad 2 (iOS 4.3.2) Macbook Pro (10.6.6)
Nokia 5800 phone FW 62.0.0125
 

The Following 4 Users Say Thank You to skatebiker For This Useful Post:
fragos's Avatar
Posts: 900 | Thanked: 273 times | Joined on Aug 2008 @ Fresno CA USA
#2
It's nice to see an objective evaluation.
__________________
George Fragos
Internet Coach & Writer
Maemo Mapper HowTo
Personal Blog -- 3 Joe's Blog


N810 -- 5.2010.33-1
 
eiffel's Avatar
Posts: 600 | Thanked: 742 times | Joined on Sep 2008 @ England
#3
Compared to 0.62 seconds with Firefox 3.0 on my three-year-old PC. Can't fit that in my pocket though.
 
Posts: 1,213 | Thanked: 356 times | Joined on Jan 2008 @ California and Virginia
#4
0.75 on 5 year-old Win7 work laptop FF 3.5
0.30 on my 2.4 GHz Quad
23.1 MicroB
6.81 Tear

Your tablet is faster than mine
__________________
----------------------------------------------------

www.ezschool.com - The best online educational experience.

Last edited by Thesandlord; 2009-07-25 at 02:55.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#5
Originally Posted by eiffel View Post
Compared to 0.62 seconds with Firefox 3.0
Mine reported various numbers between 0.31" and 0.77". But the tablet's native performance still runs rings around any javascript implementation:

Code:
~ $ echo 2^1000 | time -v bc
10715086071862673209484250490600018105614048117055336074437503883703\
51051124936122493198378815695858127594672917553146825187145285692314\
04359845775746985748039345677748242309854210746050623711418779541821\
53046474983581941267398767559165543946077062914571196477686542167660\
429831652624386837205668069376
	Command being timed: "bc"
	User time (seconds): 0.01
	System time (seconds): 0.00
	Percent of CPU this job got: 62%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0m 0.03s
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 0
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 179
	Voluntary context switches: 1
	Involuntary context switches: 9
	Swaps: 0
	File system inputs: 0
	File system outputs: 0
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#6
Well, I would be really surprised if it didn't
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#7
Originally Posted by Bundyo View Post
Well, I would be really surprised if it didn't
True, just saying that at that many orders of magnitude slower the various javascript engines still have some way to go before they can be taken seriously. Frankly all the talk going around abour WRTs, xulrunner etc on tablets scares me...
 
Posts: 4,030 | Thanked: 1,633 times | Joined on Jul 2007 @ nd usa
#8
benchmark on 2^1000 radix10 precision40
desktop PC
Safara 4beta---0.27
Chrome 2 ------ 0 .55
FF 3----------0.57
IE 8 --------1.05

N800 MMC boot
Tear 5.6
Midori 5.7
digia@web 8.3
microB 23.5 on demand 165
22.7 performance 400

Mer.14 Midori 7.1

770 2008He
Tear 9.4
MicroB 37

Measured in seconds, the smaller the number, the faster. Tear is 4X faster than microB both in N800 and 770
bun

Last edited by bunanson; 2009-07-25 at 12:35.
 
Posts: 542 | Thanked: 117 times | Joined on Sep 2008 @ 52 N, 6 E
#9
Originally Posted by lma View Post
Mine reported various numbers between 0.31" and 0.77". But the tablet's native performance still runs rings around any javascript implementation:

Code:
~ $ echo 2^1000 | time -v bc
10715086071862673209484250490600018105614048117055336074437503883703\
51051124936122493198378815695858127594672917553146825187145285692314\
04359845775746985748039345677748242309854210746050623711418779541821\
53046474983581941267398767559165543946077062914571196477686542167660\
429831652624386837205668069376
	Command being timed: "bc"
	User time (seconds): 0.01
	System time (seconds): 0.00
	Percent of CPU this job got: 62%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0m 0.03s
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 0
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 179
	Voluntary context switches: 1
	Involuntary context switches: 9
	Swaps: 0
	File system inputs: 0
	File system outputs: 0
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0
How did you do this ? Probably not from the standard unix command line.


More results:

Firefox 3.0.11 0.47 sec
Opera 9.64 0.74 sec

Tested on Sony Vaio 2.0 GHz running Kubuntu 8.10.

Nokia 5800 browser was unable to calculate, 2^500 took 5.53 sec, probably a javascript compatibility error.

Maybe stupid question, but a 400 MHz processor is five times slower than a 2 GHz, why are times more than ten times as slow even in the fastest browser ?
__________________
Nokia N810 FW version 5.2008.43-7
iPad 2 (iOS 4.3.2) Macbook Pro (10.6.6)
Nokia 5800 phone FW 62.0.0125
 
Posts: 542 | Thanked: 117 times | Joined on Sep 2008 @ 52 N, 6 E
#10
Posted twice, because my browser did not respond .....



Originally Posted by lma View Post
Mine reported various numbers between 0.31" and 0.77". But the tablet's native performance still runs rings around any javascript implementation:

Code:
~ $ echo 2^1000 | time -v bc
10715086071862673209484250490600018105614048117055336074437503883703\
51051124936122493198378815695858127594672917553146825187145285692314\
04359845775746985748039345677748242309854210746050623711418779541821\
53046474983581941267398767559165543946077062914571196477686542167660\
429831652624386837205668069376
	Command being timed: "bc"
	User time (seconds): 0.01
	System time (seconds): 0.00
	Percent of CPU this job got: 62%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0m 0.03s
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 0
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 179
	Voluntary context switches: 1
	Involuntary context switches: 9
	Swaps: 0
	File system inputs: 0
	File system outputs: 0
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0
Originally Posted by lma View Post
Mine reported various numbers between 0.31" and 0.77". But the tablet's native performance still runs rings around any javascript implementation:

Code:
~ $ echo 2^1000 | time -v bc
10715086071862673209484250490600018105614048117055336074437503883703\
51051124936122493198378815695858127594672917553146825187145285692314\
04359845775746985748039345677748242309854210746050623711418779541821\
53046474983581941267398767559165543946077062914571196477686542167660\
429831652624386837205668069376
	Command being timed: "bc"
	User time (seconds): 0.01
	System time (seconds): 0.00
	Percent of CPU this job got: 62%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0m 0.03s
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 0
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 179
	Voluntary context switches: 1
	Involuntary context switches: 9
	Swaps: 0
	File system inputs: 0
	File system outputs: 0
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0
How did you do this ? Probably not from the standard unix command line.


More results:

Firefox 3.0.11 0.47 sec
Opera 9.64 0.74 sec

Tested on Sony Vaio 2.0 GHz running Kubuntu 8.10.

Nokia 5800 browser was unable to calculate, 2^500 took 5.53 sec, probably a javascript compatibility error.

Maybe stupid question, but a 400 MHz processor is five times slower than a 2 GHz, why are times more than ten times as slow even in the fastest browser ?
 

The Following User Says Thank You to skatebiker For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 23:13.