Closed Bug 10438 Opened 26 years ago Closed 9 years ago

[FEATURE] implement platform-specific async I/O

Categories

(Core :: Networking: File, enhancement, P3)

Product:
Core
Component:
Networking: File
Platform:
All
Other
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: warrensomebody, Unassigned)

References

Details

(Keywords: helpwanted, perf, Whiteboard: [PDT-]) 

We need to replace the file transport (in nsFileChannel.cpp) with an async I/O
implementation for the various platforms. The primary ones I'm concerned about
are Mac and Win95. This will eliminate the pool of file transport threads, and
should greatly increase performance.

Rick and Scott: If you want to sign up for this, feel free to reassign this
bug.
Whiteboard: [Perf]
Putting on [Perf] radar.
Target Milestone: M9
Blocks: 10730
Assignee: warren → scc
Assigning to scc.
Assignee: scc → sdagley
I'm swamped and this is right up Steve's alley.  Steve, if you don't have time
for this, then I guess you'll have to assign it back to me, and I'll decommit on
something else.
Is this a requirment for M9 or could I defer it to M10 (since we seem to be
functional now)?  I'd be glad to do the work but I'm overcommitted on M9 already.
Target Milestone: M9 → M10
Defer to M10 -- this is a performance thing. We want to eliminate unnecessary
threads when running on Mac.
Status: NEW → ASSIGNED
Target Milestone: M10 → M11
Is this one bug for Mac & Windows (since the platform reads All)?  If so, we need
to split them up and I claim this bug # for the Mac.  I'm also shifting the Mac
work to M11 since I've already got M8 and M9 tasks that landed in M10.
No, let's just keep this as one bug and focus on the Mac first. It's the most
important platform to do this for.
Blocks: 12838
No longer blocks: 12838
Target Milestone: M11 → M14
per discussion with warren this doesn't need to be addressed pre-beta and is
gated by some Necko changes he needs to make so deferring to post-beta
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
Target Milestone: M14 → M17
My last discussion with warren on this topic indicated that there was now only a
single file transport thread so this may become a WONTFIX.  Moving to M17 for now
since even if it will still be implemented it can be done later.
Target Milestone: M17 → M14
As far as I know, we were still planning on doing this. This will affect cache
performance, so we should at least experiment to see how big of a win this would
be. Moving back to m14.
Summary: implement platform-specific async I/O → [FEATURE] implement platform-specific async I/O
featuring
Keywords: perf
Bulk add of "perf" to new keyword field.  This will replace the [PERF] we were
using in the Status Summary field.
Blocks: 15681
putting on beta1 radar, per beta criteria priority #2 - performance. Mac 
performance is the worst, and this bug touches on two Mac bottlenecks - file I/O 
and threads.
Keywords: beta1
cc waterson
Here, catch David
Assignee: sdagley → davidm
Status: ASSIGNED → NEW
Need data on how much slower.  Which area of performance?  Page load?
Whiteboard: [Perf]
PDT- unless we get data relating the performance problem to the beta1 criteria
Whiteboard: [PDT-]
m15. Will try to get performance data before deciding to do all this work.
Target Milestone: M14 → M15
assign to stop the spam
Status: NEW → ASSIGNED
Although this might be a  big win for the mac, it's hard and a major change.
HELP WANTED.
Assignee: davidm → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted
Clearly this is not an M15 stopper.  
Since it is listed as help wanted, I'm pushing it to M30, to indicated that it 
is no longer scheduled for a Nav 6 release (unless someone steps up to the 
plate).
Target Milestone: M15 → M30
Keywords: beta1
spam, changing qa contact from paulmac to tever@netscape.com on networking/RDF 
bugs
QA Contact: paulmac → tever
mass move, v2.
qa to me.
QA Contact: tever → benc
Is this DOA or should it stay helpwanted?
dougt's the file transport person, as I understand it.
I don't see this happening anytime soon.  It would be a nice task for someone 
looking to get involved in mozilla.
Assignee: nobody → dougt
Target Milestone: --- → mozilla1.0
what is milestone "mozilla1.0" anyway?  Moving to future.
Target Milestone: mozilla1.0 → Future
Component: Networking → Networking: File
Severity: major → enhancement
doug: any reason this should still stay open? from the original description, Mac
probably meant Mac OS classic (gone), and Win95 (and Win98) are on the edge of
unsupported-ness.

mass reassigning to nobody.
Assignee: dougt → nobody
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.