Closed Bug 245357 Opened 21 years ago Closed 19 years ago

very small byte size when writing to inbox (stored in a network share)

Categories

(MailNews Core :: Database, defect)

Product:
MailNews Core
Component:
Database
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: tekagi, Assigned: Bienvenu)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322) Build Identifier: Mozilla 1.6 (Mozilla/5.0;U;Windows NT 5.1;de-AT;rv:1.6) Gecko/20040113 I have a problem with Mozilla 1.6, when it comes to receiving new emails in the Inbox. These emails are written to the inbox file (which is store in a network share) in chunks of 74 bytes (observed by filemon -> see Log). This slows down the process of receiving emails, if the email folders reside on an network drive. Since this network drive should be encrypted, receiving emails with attachment of some hundred kByte is very, very slow (2 minutes for 2 MByte). Test without encryption -> 1,4 MB in 40 seconds Test with encryption -> 1,4 MB in 105 seconds A solution would be to define the byte size of the write process. Is it possible? (note: problem does not occur with latest Netscape version, but here the inbox is written to in chunks of 4 kByte block size). Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Write more Bytes per WRITE Step (Like Netscape -> 4096 Byte; at the moment on Mozilla 1.6 -> 74 Byte) Mozilla made ca 50000 WRITE for a mail with 1,4 MB attached. For the same procedure Netscape need ca 1000 WRITE. Here a part of the filemon log: 281 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 282 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230575 Length: 74 283 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 284 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230649 Length: 74 285 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 286 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230723 Length: 74 287 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 288 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230797 Length: 74 289 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 290 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230871 Length: 74 291 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 292 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8230945 Length: 74 293 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 294 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231019 Length: 74 295 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 296 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231093 Length: 74 297 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 298 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231167 Length: 74 299 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 300 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231241 Length: 74 301 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 302 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231315 Length: 74 303 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 304 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231389 Length: 74 305 18:01:58 mozilla.exe:596 QUERY INFORMATION Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS FileStandardInformation 306 18:01:58 mozilla.exe:596 WRITE Z:\verschl\moz\mail\192.168.100.10\Inbox SUCCESS Offset: 8231463 Length: 74
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.