So you are an SSD advocate, yes? SSD good, traditional HD bad sort of guy?
Naturally then SSD has no problems in your eyes...but, we know from this thread that 'Smart' status is disabled if TRIP is enabled, and, from your implication, SSD's don't behave 100% smoothly with databases, presumably with lots of SQL read/write queries... to be continued?
Saw this, I borrowed.** Interesting concept if present W7 identity
issues with TRIM are superceded by more intelligent controller/GC
algorithms -- "Real Time" being an apparent proposal (below), the onus
then (I'll start by making this up...) being shifted to favor a
controller dispersion of write-erase/rewrites cycles, over equi-
distribution and into SSD memory available, for a factor lending to
the least significant wear only over any addressable range available
(an area yet unwritten to), over all widest ranges possible.
Of course, it goes without saying, for a cost premium on the latest
and greatest in between times for implementation and distribution
(within 6 months might be guesstimeable).
Say, then, that for one SSD, 3/4 is occupied with written immutably in
occupied reluctance, for permeance of a temporal dispensation shifted
to an ensuing 1/4 portion;- whereas reverse that same ratio on a
second SDD, that will exhibit 3/4 greater permeance distribution in
direct correlation to longevity. The presumption being at what point
failure to write memory is identified, how accountable, if at all, and
to what tolerances of progressively increasing diminishability as the
SDD then effectively shrinks in size due to a brunt of writes being
shifted to a residual remainder.
**
well on that one i agree alfa, there is alot of headway being made
with the garbage collection features using idillinx onboard ARM
processor. nice thing about this built in programming set:
1. OS independent...works with anything
2. does not create performance issues as it is not another command set
being issued.
3. headless....no thought required (like TRIM)
OCZ and idillinx are almost done with a new version of this (Firmware
4.5) that will run in real time. it is auto trim basically. the
version that i am currently using only works when your array or disk
has been idle for a certain amount of time.
The TRIM spec has many drawbacks, such as I/O overhead. there is much
talk of this new GC actually being used in preference of trim. The
next gen of devices, sandforce and jetstream, are going to rely
heavily on these features. it will be interesting if Intel follows
suit.