You don’t seem to understand modern filesystems or modern hardware like some of us. -- Gary L. Wade https://www.garywade.com/ <http://www.garywade.com/>
> On Jan 7, 2023, at 3:29 PM, Gabriel Zachmann <z...@cs.uni-bremen.de> wrote: > > *Maybe* ... > that would mean that the filesystem performs predictive caching like the > CPU's cache / memory management does ... > > Also, I think you might even get worse performance: imagine several threads > reading different files *at the same time* - those files could lie on > different HD cylinders far apart from each other, so the disk heads would > have to move back and forth during those concurrent read operations, wouldn't > it? unless the disk would do some very clever caching / batching / prediction > itself ... > > G. > >> Since file systems and the associated hardware are designed to be efficient >> by caching data and knowing things like where one file or block is in >> relation to another, there’s a possibility these mechanisms could work to >> your advantage, pulling in the data while “in the neighborhood.” There’s no >> guarantee, of course, but I feel it’s worth considering. >> -- >> Gary L. Wade >> http://www.garywade.com/ >> >>> On Jan 7, 2023, at 10:37 AM, Gabriel Zachmann via Cocoa-dev >>> <cocoa-dev@lists.apple.com> wrote: >>> >>> So, why would would several threads loading those images in parallel help >>> here? In my thinking, they will just compete for the same resource, i.e., >>> hard disk. >>> >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
