Henrik Sundberg wrote:
I'd say that smaller files are faster than bigger.

The slow down due to the size increase is infinitesimal. See below for an example. It's like arguing that you should use small variables in your python program because that will make the file faster. Anyone who knows how to program knows that that's a stupid idea.

Memory is slow.

No, memmory is fast. Transfer rates of 1,000-2,000 MB/sec means that for a 50-page document (details below) you can expect to save at most 0.00014 seconds by using smaller tags.

Disks are slow.

The transfer rate of an IDE disk is in the order of 100MBits/second. The INGOTs handbook is a 50-page document with lots of tables. It is 192Kb. So the disk access part of the process contributes 0.015 seconds to the loading speed. I just wrote a perl program to remove all the paragraph and table tags (this is unreasonable of course, since you still have to have some tag). The result was 48kb. This means that, for this document, using small tags would save you *less* than 0.011 seconds in loading time. And in exchange for that you would get a more buggy program.

Hashing long strings is slower
than hashing short ones (for symbol table look up).

No, symbol look up for a longer symbol is *not* slower.

Parsing shorter
files takes less time than parsing longer ones.

False. Using a <tag-with-a-long-name> is not slower than <t>.

It takes longer time to start large programs as well.

Irrelevant comparison. Document files are not programs. OOo is a 60 MB program, not a 192kb document. OOo does rendering, memmory allocation, loads external libraries, runs threads, and does a zillion other things that documents don't do.

Cheers,
Daniel.
--
     /\/`) http://oooauthors.org
    /\/_/  http://opendocumentfellowship.org
   /\/_/  No trees were harmed in the creation of this email.
   \/_/   However, a significant number of electrons were
   /      were severely inconvenienced.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to