VisorCentral.com
Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Visor & Deluxe (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=1)
-- Speed (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=542)


Posted by Belthasar on 11-07-1999 06:21 PM:

Question

Ok, so I know mostly what makes the Visor better than a Palm, but what about raw SPEED?? which is faster?


Posted by Nutt on 11-07-1999 07:01 PM:

Post

The visor is about 50% faster then the palm V. I dont know if its faster then the palm Vx. The reason is because they optimised the hardware and software to run better.


Posted by dennya on 11-07-1999 07:12 PM:

Exclamation

Actually, it's because they eliminated the wait states... If you run CruiseControl on a Palm IIIx, you get approximately the same speed as a Visor (158% normal).

What the heck were those wait states doing in there in the first place, that's what I want to know...


Posted by mike1in3 on 11-07-1999 07:18 PM:

Post

Not only that, but I think OS 3.3 eliminates the wait states as well, just like 3.1h in the Visors.

MJH <><


Posted by jonpod on 11-08-1999 01:49 AM:

Post

My Palm V with 3.3 w/o CC is 100% Benchmark

With CC 148%
With CC and StreakHack - 161%
With CC/StreakHack and Afterburner 2.0 - 259%

Looks like the handspring guys did something like CC and Streakhack so Afterburner should still work with them.

Overclock at your own risk

jonpod


Posted by Zippy on 11-08-1999 05:14 AM:

Post

With CC/StreakHack and Afterburner 2.0 - 259%

Whoa! That's some markup. Would definitely like to see a similar benchmark run with the Visor and these apps installed.


Posted by ragamuffinn on 11-08-1999 07:36 AM:

Post

None of you are getting wait states? I'm getting them most of the time when I access the info and delete dialogues. Am I the only one?

thanks,
Chris


Posted by PDAENVY on 11-08-1999 02:06 PM:

Post

There seems to be some confusion about the term "wait state". It is a computer architecture term refering to 1 or 2 CPU cycle pauses which are designed into a system to accomodate differences in speed between various chips.

It does not refer to delays seen by a user.

A system can be designed without wait states, but it takes more effort, and thereby more time and expense. Wait states can be removed after the fact (often with noticable results - cf Afterburner), but it is not usually supported by the manufacturer. This is because it is possible that system components will be out of sync and not work properly if wait states are removed. There's no way to know except to try it.

At least that's what I remember about it from my computer engineering degree.


All times are GMT. The time now is 01:38 AM.
Show 20 posts from this thread on one page

Powered by: vBulletin Version 2.3.4
Copyright © Jelsoft Enterprises Limited 2000 - 2016.