|
High read speed - but very poor write speed is whats reported.
Also, sequential access seems fast, but direct access isn't. i.e., reading a large file in sequential chunks - a video - is fast. Reading many parts of a file in no sequential order - a dictionary or program - seems slow.
Calligraper really doesn't like being installed in the BIS - but if you move the recognition engine and the dictionaries to a high speed SD or RAM, recognition reliability increases. The culprit in this case is that Calligrapher will always give its best guess in a configurable amount of time. With the engine stored on the BIS, more of that time is spent accessing rather than processing.
For most programs, segments are loaded into RAM at first execution so speed isn't affected. For those apps which access large amounts of data regularly, the BIS is a bottleneck.
Here are some examples as far as my experience goes:
Games - Alright - most load and buffer in the RAM. Loading is sequential so fast enough to be unnoticeable.
Reference - Poor. This includes dictionaries, maps, sophisicated programs, etc. Its due to the way data is arranged - often using binary trees or similar which precludes sequential access.
Applications - Alright - most are sensibly segmented by their compilers so load a start section, middle section and end section appropriately and entirely into RAM.
__________________
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Last edited by Ward; 05-23-05 at 10:02 AM.
|