To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=50983
User sb changed the following:
What |Old value |New value
================================================================================
CC|'' |'sb'
--------------------------------------------------------------------------------
Status|CLOSED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|INVALID |
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jul 6 08:31:16 -0700
2005 -------
As sseppala pointed out on [email protected] on July 6, 2005 ("Re: [dev] Saving
document creates a lot of network traffic"): "I just did some testing and found
out that it is the hyperlinks that make saving my 109Kb .odt document to a
network drive cause 33,8 Mb of network traffic. It appears that when OO is
parsing the document for saving, each hyperlink it comes across causes it to go
open and close the folder of the document and the document it self several
times. This of course couses lot of delay and network traffic overhead. When
saving to a local harddisk this is not a big issue because delays are so short,
but when saving to a network drive it becomes extremely slow if document has
lots of hyperlinks."
The document contains lots of internal references of the form <#IDxx>. When
saving the document, this leads to lots of calls to
URIHelper::normalizedMakeRelative with a baseUriReference argument of
<file:///T:/network_save_test.odt/content.xml> (which is the same for all calls)
and a uriReference argument of <#IDxx> (which is different for different calls).
Internally in URIHelper::normalizedMakeRelative, normalizing the given
baseUriReference causes the excessive network traffic (which, by the way, is to
some extend a problem of SMB, which does not cache data; trying this with NFS,
which caches more aggresively, shows no time differences compared to a local
store).
sb->mib: This issue affects load/save performance. As there is no good
solution to caching the result of repeatedly normalizing
<file:///T:/network_save_test.odt/content.xml> within
URIHelper::normalizedMakeRelative (under what conditions should any cached data
be considered stale?), how about caching the information up the call stack?
That is, I could extend URIHelper with
rtl::OUString normalize(rtl::OUString const & uriReference)
and instead of calling URI::normalizedMakeRelative (or
URI::simpleNormalizedMakeRelative) you would call some non-normalizing
"makeRelative" function with pre-normalized input while saving.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
