Open Bug 456603 Opened 17 years ago Updated 1 year ago

get rid of Windows stat cache

Categories

(Core :: XPCOM, defect)

x86
Windows XP
defect

Tracking

()

REOPENED

People

(Reporter: jaas, Unassigned)

References

(Blocks 2 open bugs)

Details

Attachments

(2 files)

This is the Windows part of bug 307815, we don't have to remove stat caches for all platforms at the same time. Our current stat caches are fundamentally flawed, we should remove them.
Blocks: 307815
No longer depends on: 456435
Attached patch fix v1.0Splinter Review
Basic try server run shows no significant perf impact, we'll see better numbers when this lands on trunk.
Attachment #340064 - Flags: review?(doug.turner)
Attachment #340064 - Flags: review?(doug.turner) → review+
Attachment #340064 - Flags: superreview?(doug.turner)
Comment on attachment 340064 [details] [diff] [review] fix v1.0 drop the braces for one liners. if (aFileSize != -1 && SetEndOfFile(hFile)) { - MakeDirty(); rv = NS_OK; } assuming that this does not cause any performance regression as mentioned in bug 307815, this is fine.
Attachment #340064 - Flags: superreview?(doug.turner) → superreview+
landed on trunk
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
backed out because of tbox issues, not necessarily anything wrong with the patch
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This might have caused a performance regression on Tp on Vista (some 30% increase). It is confusing though since the first talos runs also supposedly included the backout, but Tp consistently went up on all 4 Vista talos machines then back down again one cycle later. This was the only patch liable to have impacted, but not sure what is going on. Might be good to land in a quiet tree next time.
Attached file windows errors
this is a text file containing the unit test errors that came up
Assignee: joshmoz → nobody
Blocks: 410005
Severity: normal → S3

I think this is worth revisiting. I can't imagine that stat() is performance-critical these days, even on Windows.
Is there a good reason not to ditch the stat cache?
If so, there should at least be a note added to nsIFile!

If anyone has any strong opinion either way, NI me if you'd like me to work up a patch.

(It just bit me in Thunderbird - Bug 1900172).

Wanting to bring data to this I threw a quick and dirty patch that bypassed the stat cache and ran it through our performance tests. Tests on a single revision are not super reliable but nothing jumped out as a regression so this seems like something we could do.

https://treeherder.mozilla.org/perfherder/compare?originalProject=try&originalRevision=a07238f2e1ac5ac7e45425563442b8164e4d08a4&newProject=try&newRevision=621fea9c0d82ba54813466842923443e939d7711&page=1

See Also: → 1900172
Blocks: 1022704
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: