large file sizes
After some testing, it appears the current GRML browsers do not support large file sizes well. The primary problem is their inability to effeciently process the data without bloating the requirements of RAM.Bar Graphs software
Data entry software
Inventory software
Backlinks (Link popularity)
Bar Graphs software
Data entry software
Inventory software
Backlinks (Link popularity)
A good example of RAM bloat is opening a file, with a size of 1 MB. (Any file size demonstrates this, but 1 MB is a nice measure to use for comparison.) Typically, if a file has 1 MB of data, the browser RAM requirements increase 1 MB. At least, this is the ideal.
Bar Graphs software
Data entry software
Inventory software
Backlinks (Link popularity)
Suppose you are using Pioneer Report MDI. You open a 1MB file. The RAM requirements jump 16 times more than the size of the file. This means a 16 MB increase in the RAM needed to display the file. In my opinion, this is not very efficient.
Subsequent versions of GRML browsers will substantially limit the RAM requirements of all files. However, for the next version of Pioneer Report MDI, this limitation is not improved. Why? It provides an incentive for users to purchase the product, rather than use it for free.
Bar Graphs software
Data entry software
Inventory software
Backlinks (Link popularity)
Bar Graphs software
Data entry software
Inventory software
Backlinks (Link popularity)
posted by Don Marchand @ 4:44 PM
<< Home