Re: The Point of Object Classes
Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance
Date: Mon, 24 Jan 2005 18:01:45 -0800
>When you write to the disk, for instance, even if you use assembler,
>chances are you will not worry what the cylinder, head, and sector will be
>on the disk drive, nor physical address, nor what brand of disk drive.
How does that pertain to objects? I fail to comprehend the correlation
between that and, "Objects enable, allow, facilitate, assist with, or make
possible higher level coding."
Relevant Pages
- Re: A Silly Database Question
... The term "cylinders" does come up repeatedly when discussing stacked disk platters at the physical level. ... When a spindle holds a stack of disk platters, there is one head for each surface that's actually used. ... If you put all these tracks together, they make up a "cylinder". ... Those disks were quite small in capacity, the 2311's of the early 1960's were about 10 Mega-bytes in capacity, the 2314's of the mid-1960's bumped that to about 30 Mbytes and by the mid-1980's a typical disk was about 300 Mbytes, so a bank might approach a couple of Giga-bytes in capacity. ...
(comp.databases) - Re: Bad Clusters
... On one of the external drives, ... indicating the clusters were not really fixed by Windows, ... > head positioning wobble that reduces accuracy of pickup, ... i.e. where the head touches the disk and thus damages it. ...
(microsoft.public.windowsxp.general) - Re: Bad Clusters
... >drives I use for backup. ... head positioning wobble that reduces accuracy of pickup, ... Why would a previously good HD develop a bad sector? ... i.e. where the head touches the disk and thus damages it. ...
(microsoft.public.windowsxp.general) - Re: Perhaps SCO has a legitimate gripe
... >>you, when they realize its their head on the block, they usually ... One department orders a new Model 80 IBM and he was heard ... > That machine was to be their first AIX on Intel. ... So some of these disk sets were inserted ...
(comp.unix.sco.misc) - Re: Higher than expected disk write(2) latency
... You write sector n and n+1, it takes some amount of time for that first set of sectors to come under the head, when it does you write it and immediately return. ... If the sector was randomly placed in the rotation (ie 50% chance of the disk being off by 1/2 a rotation or less-you would have a 4.15 ms average seek time for your test)-but the case of sequential sync writes this leaves the sector about as far as possible from the head. ... Almost the same case as for the 7200 rpm disk, but I bet these SAS drives are 15k drives? ...
(Linux-Kernel) |
|
