http://bugzilla.novell.com/show_bug.cgi?id=557609
http://bugzilla.novell.com/show_bug.cgi?id=557609#c9
Michael Matz changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|matz@novell.com |
--- Comment #9 from Michael Matz 2010-06-25 12:05:33 UTC ---
The values in comment #7 strace log are completely bollocks. Repeated fadvices
on files 10,11,12,13,17 with sizes and offsets being nonsensical:
E.g.:
370 1269684166.071359 fadvise64(13, 3422535680, 8388608, POSIX_FADV_WILLNEED)
370 1269684166.290542 fadvise64(12, 1653669888, 7274496, POSIX_FADV_WILLNEED)
So, file 13 at offset 3.4 GB, reading 8MB in size. And so on ...
Unfortunately the strace doesn't show us which files are connected with those
file descriptors. But files of such size can't possibly be interesting
files to preload. Such files normally shouldn't be involved in the startup
process at all. One guess would be for instance some log file gone wild,
that the preload tracer sees as being opened and hence like to read in
completely.
Instead of introducing an artificial limit on filesize (size > N --> don't
preload at all), or on read data size (ala always read in N MB max, per file),
I'd first like to know which files are the ones being so large.
But as stop-gap measure, I do think it makes sense to not preload, say,
8 MB per file (or to ignore all files > say 16 MB, this needs to be a bit
large so as to not ignore some of the very large shared libraries we have).
One other idea: if the above files are indeed logfiles or the like, then
they are probably opened O_WRONLY. We can map such open calls to just
being stat()s, instead of causing a full read-in.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.