Ciao, avrei un quesito da porre (forse stupido)
Due hd con pari caratteristiche (marca, capienza, numero di giri) ma aventi buffer cache diversi (uno 2mb e l'altro 8mb) si nota molto la differenza?
Grazie a tutti:o

nn credo sia una differenza così percettibile, però se fai i test un pò di differenza c'è...

...prestazionalmente non c'è praticamente nessuna differenza. Se c'è differenza non è in un ordine di grandezza che può cambiare le prestazioni del nostro pc...e non ho mai letto un articolo che dicesse il contrario.

...ciao!

Il buffer è un'area particolare della memoria la cui informazione rimane in attesa di essere smistata verso un dispositivo o l'applicativo che deve elaborarla. Logico quindi che la differenza tra un hdd con buffer da 2 mb da uno da 8 mb si vedrà maggiormente maggiori saranno le dimensioni del file che viene copiato...

:DGrazie raga, sempre disponibili ed esaurienti

direttamente da wikipedia.org
"Disk buffer

(also known as disk cache or cache buffer)

Hard disks have historically often been packaged with embedded computers used for control and interface protocols. Since the late 1980s, nearly all disks sold have these embedded computers and either an ATA, SCSI, or Fibre Channel interface. The embedded computer usually has some small amount of memory which it uses to store the bits going to and coming from the disk platter.

The disk buffer is physically distinct from and is used differently than the page cache typically kept by the operating system in the computer's main memory. The disk buffer is controlled by the embedded computer in the disk drive, and the page cache is controlled by the computer to which that disk is attached. The disk buffer is usually quite small, 2 to 16 MB, and the page cache is generally all unused physical memory, which in a 2006 PC may be as much as 2GB. And while data in the page cache is reused multiple times, the data in the disk buffer is typically never reused. In this sense, the phrases disk cache and cache buffer are misnomers, and the embedded computer's memory is more appropriately called the disk buffer.

The disk buffer has multiple uses:

    * Readahead / readbehind: When executing a read from the disk, the disk arm moves the read/write head to (or near) the correct track, and after some settling time the read head begins to pick up bits. Usually, the first sectors to be read are not the ones that have been requested by the operating system. The disk's embedded computer typically saves these unrequested sectors in the disk buffer, in case the operating system requests them later.

    * Speed matching: The speed of the disk's I/O interface to the computer almost never matches the speed at which the bits are transferred to and from the hard disk platter. The disk buffer is used so that both the I/O interface and the disk read/write head can operate at full speed.

    * Write acceleration: The disk's embedded microcontroller may signal the main computer that a disk write is complete immediately after receiving the write data, before the data are actually written to the platter. This early signal allows the main computer to continue working even though the data has not actually been written yet. This can be somewhat dangerous, because if power is lost before the data are permanently fixed in the magnetic media, the data will be lost from the disk buffer, and the filesystem on the disk may be left in an inconsistent state. On some disks, this vulnerable period between signaling the write complete and fixing the data can be arbitrarily long, as the write can be deferred indefinitely by newly arriving requests. For this reason, the use of write acceleration can be controversial. Consistency can be maintained, however, by using a battery-backed memory system in the disk controller for caching data - although this is typically only found in high end RAID controllers. Alternately, the caching can simply be turned off when the integrity of data is deemed more important than write performance.

    * Command queuing: Newer SATA and most SCSI disks can accept multiple commands while any one command is in operation. These commands are stored by the disk's embedded computer until they are completed. Should a read reference the data at the destination of a queued write, the write's data will be returned. Command queuing is different from write acceleration in that the main computer's operating system is notified when data are actually written onto the magnetic media. The OS can use this information to keep the filesystem consistent through rescheduled writes.
"

Grazie ancora a tutti....